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 updates for v4.15 (take 2)
Date: Fri, 17 Nov 2017 19:24:15 -0800 [thread overview]
Message-ID: <1510975455-30949-1-git-send-email-linux@roeck-us.net> (raw)
Hi Linus,
Please pull hwmon updates for Linux v4.15 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-for-linus-v4.15-take2
Thanks,
Guenter
------
The following changes since commit e60e1ee60630cafef5e430c2ae364877e061d980:
Merge tag 'drm-for-v4.15' of git://people.freedesktop.org/~airlied/linux (2017-11-15 20:42:10 -0800)
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.15-take2
for you to fetch changes up to 7adce422dd90bd673ef5c4da32c896bf740e3277:
hwmon: (w83793) Remove duplicate NULL check (2017-11-16 01:03:19 -0800)
----------------------------------------------------------------
hwmon updates/fixes for v4.15 - take 2
Minor bug fix in k10temp driver
Take advantage of added NULL check in i2c_unregister_device()
----------------------------------------------------------------
Andy Shevchenko (4):
hwmon: (w83781d) Remove duplicate NULL check
hwmon: (w83791d) Remove duplicate NULL check
hwmon: (w83792d) Remove duplicate NULL check
hwmon: (w83793) Remove duplicate NULL check
Guenter Roeck (1):
hwmon: (k10temp) Correct model name for Ryzen 1600X
drivers/hwmon/k10temp.c | 2 +-
drivers/hwmon/w83781d.c | 12 ++++--------
drivers/hwmon/w83791d.c | 15 +++++----------
drivers/hwmon/w83792d.c | 15 +++++----------
drivers/hwmon/w83793.c | 15 +++++----------
5 files changed, 20 insertions(+), 39 deletions(-)
reply other threads:[~2017-11-18 3:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1510975455-30949-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®