All of lore.kernel.org
 help / color / mirror / Atom feed
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 patches for 4.11-rc1
Date: Wed, 22 Feb 2017 15:55:16 +0100	[thread overview]
Message-ID: <20170222145516.GA17254@kroah.com> (raw)

The following changes since commit 49def1853334396f948dcb4cedb9347abb318df5:

  Linux 4.10-rc4 (2017-01-15 16:21:59 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/ tags/driver-core-4.11-rc1

for you to fetch changes up to 17627157cda13089d8a6c1c2d35acb07334b899c:

  kernfs: handle null pointers while printing node name and path (2017-02-10 16:02:26 +0100)

----------------------------------------------------------------
driver core patches for 4.11-rc1

Here is the "small" driver core patches for 4.11-rc1.

Not much here, some firmware documentation and self-test updates, a
debugfs code formatting issue, and a new feature for call_usermodehelper
to make it more robust on systems that want to lock it down in a more
secure way.

All of these have been linux-next for a while now with no reported
issues.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Chen Yu (1):
      platform: Print the resource range if device failed to claim

Greg Kroah-Hartman (4):
      Merge 4.10-rc4 into driver-core-next
      kmod: make usermodehelper path a const string
      Make static usermode helper binaries constant
      Introduce STATIC_USERMODEHELPER to mediate call_usermodehelper()

Jakub Kicinski (1):
      debugfs: improve formatting of debugfs_real_fops()

Jason A. Donenfeld (1):
      kref: prefer atomic_inc_not_zero to atomic_add_unless

Konstantin Khlebnikov (1):
      kernfs: handle null pointers while printing node name and path

Luis R. Rodriguez (3):
      selftests: firmware: only modprobe if driver is missing
      selftests: firmware: send expected errors to /dev/null
      firmware: revamp firmware documentation

 Documentation/driver-api/firmware/built-in-fw.rst  |  38 ++++
 Documentation/driver-api/firmware/core.rst         |  16 ++
 .../driver-api/firmware/direct-fs-lookup.rst       |  30 ++++
 .../driver-api/firmware/fallback-mechanisms.rst    | 195 +++++++++++++++++++++
 .../driver-api/firmware/firmware_cache.rst         |  51 ++++++
 .../driver-api/firmware/fw_search_path.rst         |  26 +++
 Documentation/driver-api/firmware/index.rst        |  16 ++
 Documentation/driver-api/firmware/introduction.rst |  27 +++
 Documentation/driver-api/firmware/lookup-order.rst |  18 ++
 .../driver-api/firmware/request_firmware.rst       |  56 ++++++
 Documentation/driver-api/index.rst                 |   1 +
 Documentation/firmware_class/README                | 128 --------------
 drivers/base/platform.c                            |   2 +-
 drivers/macintosh/windfarm_core.c                  |   4 +-
 drivers/net/hamradio/baycom_epp.c                  |  10 +-
 drivers/pnp/pnpbios/core.c                         |   5 +-
 drivers/staging/greybus/svc_watchdog.c             |   4 +-
 drivers/staging/rtl8192e/rtl8192e/rtl_dm.c         |   8 +-
 fs/kernfs/dir.c                                    |  10 ++
 fs/nfsd/nfs4layouts.c                              |   6 +-
 include/linux/debugfs.h                            |   3 +-
 include/linux/kmod.h                               |   7 +-
 include/linux/kref.h                               |   2 +-
 include/trace/events/cgroup.h                      |  20 +--
 kernel/kmod.c                                      |  18 +-
 security/Kconfig                                   |  35 ++++
 security/keys/request_key.c                        |   7 +-
 tools/testing/selftests/firmware/fw_filesystem.sh  |  25 ++-
 28 files changed, 594 insertions(+), 174 deletions(-)
 create mode 100644 Documentation/driver-api/firmware/built-in-fw.rst
 create mode 100644 Documentation/driver-api/firmware/core.rst
 create mode 100644 Documentation/driver-api/firmware/direct-fs-lookup.rst
 create mode 100644 Documentation/driver-api/firmware/fallback-mechanisms.rst
 create mode 100644 Documentation/driver-api/firmware/firmware_cache.rst
 create mode 100644 Documentation/driver-api/firmware/fw_search_path.rst
 create mode 100644 Documentation/driver-api/firmware/index.rst
 create mode 100644 Documentation/driver-api/firmware/introduction.rst
 create mode 100644 Documentation/driver-api/firmware/lookup-order.rst
 create mode 100644 Documentation/driver-api/firmware/request_firmware.rst
 delete mode 100644 Documentation/firmware_class/README

                 reply	other threads:[~2017-02-22 14:55 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=20170222145516.GA17254@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.