From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] hwmon fixes for v4.19-rc2
Date: Wed, 29 Aug 2018 13:32:40 -0700 [thread overview]
Message-ID: <1535574760-11636-1-git-send-email-linux@roeck-us.net> (raw)
Hi Linus,
Please pull hwmon fixes for Linux v4.19-rc2 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus-v4.19-rc2
Thanks,
Guenter
------
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git tags/hwmon-for-linus-v4.19-rc2
for you to fetch changes up to d49dbfade96d5b0863ca8a90122a805edd5ef50a:
hwmon: (nct6775) Fix potential Spectre v1 (2018-08-26 17:45:25 -0700)
----------------------------------------------------------------
hwmon fixes for v4.19-rc2
- Fix potential Spectre v1 in nct6775
- Add error checking to adt7475 driver
- Fix reading shunt resistor value in ina2xx driver
----------------------------------------------------------------
Dan Carpenter (2):
hwmon: (adt7475) Potential error pointer dereferences
hwmon: (adt7475) Make adt7475_read_word() return errors
Gustavo A. R. Silva (1):
hwmon: (nct6775) Fix potential Spectre v1
Lothar Felten (1):
hwmon: (ina2xx) fix sysfs shunt resistor read access
Documentation/hwmon/ina2xx | 2 +-
drivers/hwmon/adt7475.c | 25 +++++++++++++++++--------
drivers/hwmon/ina2xx.c | 13 +++++++++++--
drivers/hwmon/nct6775.c | 2 ++
include/linux/platform_data/ina2xx.h | 2 +-
5 files changed, 32 insertions(+), 12 deletions(-)
next reply other threads:[~2018-08-29 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 20:32 Guenter Roeck [this message]
2018-08-29 23:07 ` Linus Torvalds
2018-08-30 0:42 ` 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=1535574760-11636-1-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®