From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Driver core fixes for 4.17-rc3
Date: Fri, 27 Apr 2018 16:41:22 +0200 [thread overview]
Message-ID: <20180427144122.GA9293@kroah.com> (raw)
The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.17-rc3
for you to fetch changes up to b93815d0f37e7c4a056a143e6d782abc084ea56b:
firmware: some documentation fixes (2018-04-25 18:37:20 +0200)
----------------------------------------------------------------
Driver core fixes for 4.17-rc3
Here are some small driver core and firmware fixes for 4.17-rc3
There's a kobject WARN() removal to make syzkaller a lot happier about
some "normal" error paths that it keeps hitting, which should reduce the
number of false-positives we have been getting recently.
There's also some fimware test and documentation fixes, and the
coredump() function signature change that needed to happen after -rc1
before drivers started to take advantage of it.
All of these have been in linux-next with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Andres Rodriguez (1):
firmware: some documentation fixes
Arend van Spriel (1):
drivers: change struct device_driver::coredump() return type to void
Ben Hutchings (2):
test_firmware: Install all scripts
test_firmware: fix setting old custom fw path back on exit, second try
Dmitry Vyukov (1):
kobject: don't use WARN for registration failures
Hans de Goede (1):
firmware: Fix firmware documentation for recent file renames
Jeffrin Jose T (1):
selftests:firmware: fixes a call to a wrong function name
Documentation/driver-api/firmware/request_firmware.rst | 16 ++++++++--------
Documentation/driver-api/infrastructure.rst | 2 +-
Documentation/power/suspend-and-cpuhotplug.txt | 2 +-
drivers/base/firmware_loader/fallback.c | 4 ++--
drivers/base/firmware_loader/fallback.h | 2 +-
include/linux/device.h | 6 ++++--
lib/kobject.c | 11 +++++------
tools/testing/selftests/firmware/Makefile | 1 +
tools/testing/selftests/firmware/fw_lib.sh | 10 ++++++----
tools/testing/selftests/firmware/fw_run_tests.sh | 2 +-
10 files changed, 30 insertions(+), 26 deletions(-)
reply other threads:[~2018-04-27 14:41 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=20180427144122.GA9293@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.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 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.