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,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Saravana Kannan <saravanak@google.com>
Subject: [GIT PULL] Driver core fixes for 6.0-rc4
Date: Fri, 2 Sep 2022 17:31:03 +0200	[thread overview]
Message-ID: <YxIht+ev+gXsF6ZD@kroah.com> (raw)

The following changes since commit 1c23f9e627a7b412978b4e852793c5e3c3efc555:

  Linux 6.0-rc2 (2022-08-21 17:32:54 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-6.0-rc4

for you to fetch changes up to 789bba82f63c3e81dce426ba457fc7905b30ac6e:

  firmware_loader: Fix memory leak in firmware upload (2022-09-01 17:47:27 +0200)

----------------------------------------------------------------
Driver core fixes for 6.0-rc4

Here are some small driver core fixes for some oft-reported problems in
6.0-rc1.  They include:
  - a bunch of reverts to handle driver_deferred_probe_check_state()
    problems that were part of the 6.0-rc1 merge.
  - firmware_loader bugfixes now that the code is being properly tested
    and used by others
  - arch_topology fix
  - deferred driver probe bugfix to solve a long-suffering amba bus
    problem that many people have reported.

All of these have been in linux-next for a while with no reported
problems.

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

----------------------------------------------------------------
Florian Fainelli (1):
      arch_topology: Silence early cacheinfo errors when non-existent

Isaac J. Manjarres (1):
      driver core: Don't probe devices after bus_type.match() probe deferral

Russ Weight (2):
      firmware_loader: Fix use-after-free during unregister
      firmware_loader: Fix memory leak in firmware upload

Saravana Kannan (4):
      Revert "driver core: Delete driver_deferred_probe_check_state()"
      Revert "net: mdio: Delete usage of driver_deferred_probe_check_state()"
      Revert "PM: domains: Delete usage of driver_deferred_probe_check_state()"
      Revert "iommu/of: Delete usage of driver_deferred_probe_check_state()"

 drivers/base/arch_topology.c                |  2 +-
 drivers/base/dd.c                           | 40 +++++++++++++++++++++++++++++
 drivers/base/firmware_loader/sysfs.c        |  7 +++--
 drivers/base/firmware_loader/sysfs.h        |  5 ++++
 drivers/base/firmware_loader/sysfs_upload.c | 12 ++++++++-
 drivers/base/power/domain.c                 |  2 +-
 drivers/iommu/of_iommu.c                    |  2 +-
 drivers/net/mdio/fwnode_mdio.c              |  4 ++-
 include/linux/device/driver.h               |  1 +
 9 files changed, 66 insertions(+), 9 deletions(-)

             reply	other threads:[~2022-09-02 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 15:31 Greg KH [this message]
2022-09-02 18:02 ` [GIT PULL] Driver core fixes for 6.0-rc4 Linus Torvalds
2022-09-03  6:42   ` Greg KH
2022-09-02 18:30 ` 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=YxIht+ev+gXsF6ZD@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saravanak@google.com \
    --cc=sfr@canb.auug.org.au \
    --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