From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>
Subject: [GIT PULL] platform-drivers-x86 for 5.4-3
Date: Thu, 17 Oct 2019 12:55:20 +0300 [thread overview]
Message-ID: <20191017095520.GA8671@smile.fi.intel.com> (raw)
Hi Linus,
Few small fixes for v5.4-rc4. The bunch was in linux-next for few days.
No conflicts with current master.
Thanks,
With Best Regards,
Andy Shevchenko
The following changes since commit da0c9ea146cbe92b832f1b0f694840ea8eb33cce:
Linux 5.4-rc2 (2019-10-06 14:27:30 -0700)
are available in the Git repository at:
git://git.infradead.org/linux-platform-drivers-x86.git tags/platform-drivers-x86-v5.4-3
for you to fetch changes up to 832392db9747b9c95724d37fc6a5dadd3d4ec514:
platform/x86: i2c-multi-instantiate: Fail the probe if no IRQ provided (2019-10-14 15:31:50 +0300)
----------------------------------------------------------------
platform-drivers-x86 for v5.4-3
Users of Intel P-Unit IPC driver might be surprised by harmless warning.
Thus, switch to API which doesn't issue a warning at all.
I²C multi-instantiate driver continues to add slave devices even when IRQ
resource is not found. For devices in the market IRQ resource is mandatory,
so, fail the ->probe() of the parent driver to avoid slaves being probed.
Avoid compiler warning due to unused variable in Classmate laptop driver.
The following is an automated git shortlog grouped by driver:
classmate-laptop:
- remove unused variable
i2c-multi-instantiate:
- Fail the probe if no IRQ provided
intel_punit_ipc:
- Avoid error message when retrieving IRQ
----------------------------------------------------------------
Andy Shevchenko (2):
platform/x86: intel_punit_ipc: Avoid error message when retrieving IRQ
platform/x86: i2c-multi-instantiate: Fail the probe if no IRQ provided
yu kuai (1):
platform/x86: classmate-laptop: remove unused variable
drivers/platform/x86/classmate-laptop.c | 12 ------------
drivers/platform/x86/i2c-multi-instantiate.c | 1 +
drivers/platform/x86/intel_punit_ipc.c | 3 +--
3 files changed, 2 insertions(+), 14 deletions(-)
--
With Best Regards,
Andy Shevchenko
next reply other threads:[~2019-10-17 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:55 Andy Shevchenko [this message]
2019-10-17 16:10 ` pr-tracker-bot
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=20191017095520.GA8671@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andy@infradead.org \
--cc=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