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 5.14-rc3
Date: Fri, 23 Jul 2021 16:58:14 +0200 [thread overview]
Message-ID: <YPrZBiDr/6Y78Vda@kroah.com> (raw)
The following changes since commit 2734d6c1b1a089fb593ef6a23d4b70903526fe0c:
Linux 5.14-rc2 (2021-07-18 14:13:49 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git tags/driver-core-5.14-rc3
for you to fetch changes up to e64daad660a0c9ace3acdc57099fffe5ed83f977:
driver core: Prevent warning when removing a device link from unregistered consumer (2021-07-21 17:28:42 +0200)
----------------------------------------------------------------
Driver core fixes for 5.14-rc3
Here are 2 small driver core fixes to resolve some reported problems for
5.14-rc3. They include:
- aux bus memory leak fix
- unneeded warning message removed when removing a device link.
Both have been in linux-next with no reported problems.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Adrian Hunter (1):
driver core: Prevent warning when removing a device link from unregistered consumer
Peter Ujfalusi (1):
driver core: auxiliary bus: Fix memory leak when driver_register() fail
drivers/base/auxiliary.c | 8 +++++++-
drivers/base/core.c | 6 ++++--
2 files changed, 11 insertions(+), 3 deletions(-)
next reply other threads:[~2021-07-23 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 14:58 Greg KH [this message]
2021-07-23 17:23 ` [GIT PULL] Driver core fixes for 5.14-rc3 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=YPrZBiDr/6Y78Vda@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