From: Darren Hart <dvhart@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] platform-drivers-x86 for 4.5-2
Date: Sun, 24 Jan 2016 11:06:53 -0800 [thread overview]
Message-ID: <20160124190653.GA2694@malice.jf.intel.com> (raw)
Hi Linus,
Emergency travel prevented me from completing my final testing on this until
today. Nothing here that couldn't wait until RC1 fixes, but I thought it best to
get it out sooner rather than later as it does contain a build warning fix.
Thanks,
Darren Hart
Intel Open Source Technology Center
The following changes since commit 404a47410c26a115123885977053e9a1a4460929:
Merge branch 'uaccess' (batched user access infrastructure) (2016-01-21 13:02:41 -0800)
are available in the git repository at:
git://git.infradead.org/users/dvhart/linux-platform-drivers-x86.git tags/platform-drivers-x86-v4.5-2
for you to fetch changes up to 6b31de3e698582fe0b8f7f4bab15831b73204800:
ideapad-laptop: Add Lenovo Yoga 700 to no_hw_rfkill dmi list (2016-01-24 10:15:01 -0800)
----------------------------------------------------------------
platform-drivers-x86 for 4.5-2
A build warning fix, MAINTAINERS cleanup, and a new DMI quirk.
ideapad-laptop:
- Add Lenovo Yoga 700 to no_hw_rfkill dmi list
MAINTAINERS:
- Combine multiple telemetry entries
intel_telemetry_debugfs:
- Fix unused warnings in telemetry debugfs
----------------------------------------------------------------
Josh Boyer (1):
ideapad-laptop: Add Lenovo Yoga 700 to no_hw_rfkill dmi list
Souvik Kumar Chakravarty (2):
intel_telemetry_debugfs: Fix unused warnings in telemetry debugfs
MAINTAINERS: Combine multiple telemetry entries
MAINTAINERS | 4 +---
drivers/platform/x86/ideapad-laptop.c | 7 +++++++
drivers/platform/x86/intel_telemetry_debugfs.c | 2 ++
3 files changed, 10 insertions(+), 3 deletions(-)
--
Darren Hart
Intel Open Source Technology Center
reply other threads:[~2016-01-24 19:06 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=20160124190653.GA2694@malice.jf.intel.com \
--to=dvhart@infradead.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
Powered by JetHome