public inbox for linux-kernel@vger.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, Tejun Heo <tj@kernel.org>
Subject: [GIT PULL] Driver core patches for 4.3-rc1
Date: Thu, 20 Aug 2015 12:10:25 -0700	[thread overview]
Message-ID: <20150820191025.GA24503@kroah.com> (raw)

The following changes since commit cbfe8fa6cd672011c755c3cd85c9ffd4e2d10a6f:

  Linux 4.2-rc4 (2015-07-26 12:26:21 -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.3-rc1

for you to fetch changes up to 71db87ba570038497db1227b7dc61113c4156565:

  bus: subsys: update return type of ->remove_dev() to void (2015-08-05 17:08:14 -0700)

----------------------------------------------------------------
Driver core patches for 4.3-rc1

Here is the new patches for the driver core / sysfs for 4.3-rc1.

Very small number of changes here, all the details are in the shortlog,
nothing major happening at all this kernel release, which is nice to
see.

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

----------------------------------------------------------------
Grygorii Strashko (1):
      driver core: correct device's shutdown order

Luis R. Rodriguez (1):
      selftests: firmware: skip timeout checks for kernels without user mode helper

Masahiro Yamada (1):
      devres: fix devres_get()

Mathias Krause (2):
      cpu: Remove bogus __ref annotation of cpu_subsys_online()
      kernel, cpu: Remove bogus __ref annotations

Seymour, Shane M (1):
      sysfs.txt: update show method notes about sprintf/snprintf/scnprintf usage

Tomeu Vizoso (1):
      driver core: fix docbook for device_private.device

Viresh Kumar (1):
      bus: subsys: update return type of ->remove_dev() to void

Vladimir Zapolskiy (1):
      firmware: fix wrong memory deallocation in fw_add_devm_name()

 Documentation/filesystems/sysfs.txt               |  5 ++-
 arch/sh/kernel/cpu/sh4/sq.c                       |  3 +-
 arch/tile/kernel/sysfs.c                          | 11 ++---
 arch/x86/kernel/cpu/microcode/core.c              |  5 +--
 drivers/base/base.h                               |  3 +-
 drivers/base/core.c                               | 49 +++++++++++++++++++++++
 drivers/base/cpu.c                                |  2 +-
 drivers/base/dd.c                                 |  8 ++++
 drivers/base/devres.c                             |  4 +-
 drivers/base/firmware_class.c                     |  2 +-
 drivers/cpufreq/cpufreq.c                         | 12 +++---
 drivers/net/rionet.c                              |  4 +-
 include/linux/device.h                            |  2 +-
 kernel/cpu.c                                      | 16 ++++----
 tools/testing/selftests/firmware/fw_filesystem.sh | 25 +++++++++---
 tools/testing/selftests/firmware/fw_userhelper.sh | 12 +++++-
 16 files changed, 120 insertions(+), 43 deletions(-)

                 reply	other threads:[~2015-08-20 19:12 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=20150820191025.GA24503@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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