From: Bartosz Golaszewski <bgolaszewski@baylibre.com> To: Guenter Roeck <linux@roeck-us.net> Cc: LKML <linux-kernel@vger.kernel.org>, Benoit Cousson <bcousson@baylibre.com>, Patrick Titiano <ptitiano@baylibre.com>, LM Sensors <lm-sensors@lm-sensors.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com> Subject: [PATCH 1/2] hwmon: (ina2xx) remove an unnecessary dev_get_drvdata() result check Date: Mon, 12 Jan 2015 14:47:21 +0100 [thread overview] Message-ID: <1421070442-9635-2-git-send-email-bgolaszewski@baylibre.com> (raw) In-Reply-To: <1421070442-9635-1-git-send-email-bgolaszewski@baylibre.com> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> --- drivers/hwmon/ina2xx.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/hwmon/ina2xx.c b/drivers/hwmon/ina2xx.c index a16d6a2..ae110c5 100644 --- a/drivers/hwmon/ina2xx.c +++ b/drivers/hwmon/ina2xx.c @@ -370,9 +370,6 @@ static ssize_t ina226_set_interval(struct device *dev, unsigned long val; int status; - if (IS_ERR(data)) - return PTR_ERR(data); - status = kstrtoul(buf, 10, &val); if (status < 0) return status; -- 2.1.3
WARNING: multiple messages have this Message-ID (diff)
From: Bartosz Golaszewski <bgolaszewski@baylibre.com> To: Guenter Roeck <linux@roeck-us.net> Cc: LKML <linux-kernel@vger.kernel.org>, Benoit Cousson <bcousson@baylibre.com>, Patrick Titiano <ptitiano@baylibre.com>, LM Sensors <lm-sensors@lm-sensors.org>, Bartosz Golaszewski <bgolaszewski@baylibre.com> Subject: [lm-sensors] [PATCH 1/2] hwmon: (ina2xx) remove an unnecessary dev_get_drvdata() result check Date: Mon, 12 Jan 2015 13:47:21 +0000 [thread overview] Message-ID: <1421070442-9635-2-git-send-email-bgolaszewski@baylibre.com> (raw) In-Reply-To: <1421070442-9635-1-git-send-email-bgolaszewski@baylibre.com> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> --- drivers/hwmon/ina2xx.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/hwmon/ina2xx.c b/drivers/hwmon/ina2xx.c index a16d6a2..ae110c5 100644 --- a/drivers/hwmon/ina2xx.c +++ b/drivers/hwmon/ina2xx.c @@ -370,9 +370,6 @@ static ssize_t ina226_set_interval(struct device *dev, unsigned long val; int status; - if (IS_ERR(data)) - return PTR_ERR(data); - status = kstrtoul(buf, 10, &val); if (status < 0) return status; -- 2.1.3 _______________________________________________ lm-sensors mailing list lm-sensors@lm-sensors.org http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2015-01-12 13:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-12 13:47 [PATCH 0/2] hwmon: (ina2xx) code clean-up and minor fixes Bartosz Golaszewski 2015-01-12 13:47 ` [lm-sensors] " Bartosz Golaszewski 2015-01-12 13:47 ` Bartosz Golaszewski [this message] 2015-01-12 13:47 ` [lm-sensors] [PATCH 1/2] hwmon: (ina2xx) remove an unnecessary dev_get_drvdata() result check Bartosz Golaszewski 2015-01-12 13:47 ` [PATCH 2/2] hwmon: (ina2xx) use DIV_ROUND_CLOSEST() to avoid rounding errors Bartosz Golaszewski 2015-01-12 13:47 ` [lm-sensors] " Bartosz Golaszewski 2015-01-12 14:23 ` [PATCH 0/2] hwmon: (ina2xx) code clean-up and minor fixes Guenter Roeck 2015-01-12 14:23 ` [lm-sensors] " Guenter Roeck
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1421070442-9635-2-git-send-email-bgolaszewski@baylibre.com \ --to=bgolaszewski@baylibre.com \ --cc=bcousson@baylibre.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@roeck-us.net \ --cc=lm-sensors@lm-sensors.org \ --cc=ptitiano@baylibre.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.