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.3-rc1
Date: Thu, 2 Mar 2023 11:20:16 +0100 [thread overview]
Message-ID: <ZAB4YGjj/M9scmiQ@kroah.com> (raw)
The following changes since commit a93e884edf61f9debc9ca61ef9e545f0394ab666:
Merge tag 'driver-core-6.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core (2023-02-24 12:58:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-6.3-rc1_2
for you to fetch changes up to 0c058fb94ae0e2a68639f4569de1c3abf5df7ad7:
driver core: fw_devlink: Print full path and name of fwnode (2023-02-25 10:52:02 +0100)
----------------------------------------------------------------
Driver core fixes for 6.3-rc1
Here is another small set of driver core patches for 6.3-rc1
They resolve some reported problems with the previous driver core
patches that are in your tree.
They solve a problem with the bus_type cleanup as reported and fixced by
Geert, and 2 fw_devlink changes to make debugging problems easier.
There is one known outstanding problem with the fw_deflink changes in
your tree that is still being worked on, and it looks like a clk core
change will be submitted soon for that, probably after 6.3-rc1.
All 3 of these have been in linux-next with no reported problems (only
reports that they fixed problems.)
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Geert Uytterhoeven (1):
driver core: bus: Handle early calls to bus_to_subsys()
Saravana Kannan (2):
driver core: fw_devlink: Avoid spurious error message
driver core: fw_devlink: Print full path and name of fwnode
drivers/base/bus.c | 2 +-
drivers/base/core.c | 12 ++++++------
2 files changed, 7 insertions(+), 7 deletions(-)
next reply other threads:[~2023-03-02 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 10:20 Greg KH [this message]
2023-03-02 18:34 ` [GIT PULL] Driver core fixes for 6.3-rc1 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=ZAB4YGjj/M9scmiQ@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