The patch titled
Subject: drivers/scsi: replace strict_strto calls
has been removed from the -mm tree. Its filename was
drivers-scsi-replace-strict_strto-calls.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Daniel Walter <dwalter@xxxxxxxxxx>
Subject: drivers/scsi: replace strict_strto calls
Replace obsolete strict_strto with more appropriate kstrto calls
Signed-off-by: Daniel Walter <dwalter@xxxxxxxxxx>
Cc: "James E.J. Bottomley" <JBottomley@xxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/scsi/pmcraid.c | 4 ++--
drivers/scsi/scsi_sysfs.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff -puN drivers/scsi/pmcraid.c~drivers-scsi-replace-strict_strto-calls drivers/scsi/pmcraid.c
--- a/drivers/scsi/pmcraid.c~drivers-scsi-replace-strict_strto-calls
+++ a/drivers/scsi/pmcraid.c
@@ -4213,9 +4213,9 @@ static ssize_t pmcraid_store_log_level(
{
struct Scsi_Host *shost;
struct pmcraid_instance *pinstance;
- unsigned long val;
+ u8 val;
- if (strict_strtoul(buf, 10, &val))
+ if (kstrtou8(buf, 10, &val))
return -EINVAL;
/* log-level should be from 0 to 2 */
if (val > 2)
diff -puN drivers/scsi/scsi_sysfs.c~drivers-scsi-replace-strict_strto-calls drivers/scsi/scsi_sysfs.c
--- a/drivers/scsi/scsi_sysfs.c~drivers-scsi-replace-strict_strto-calls
+++ a/drivers/scsi/scsi_sysfs.c
@@ -910,9 +910,9 @@ sdev_store_queue_ramp_up_period(struct d
const char *buf, size_t count)
{
struct scsi_device *sdev = to_scsi_device(dev);
- unsigned long period;
+ unsigned int period;
- if (strict_strtoul(buf, 10, &period))
+ if (kstrtouint(buf, 10, &period))
return -EINVAL;
sdev->queue_ramp_up_period = msecs_to_jiffies(period);
_
Patches currently in -mm which might be from dwalter@xxxxxxxxxx are
origin.patch
linux-next.patch
include-linux-remove-strict_strto-definitions.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
