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,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Saravana Kannan <saravanak@google.com>
Subject: [GIT PULL] Driver core fixes for 6.9-rc5
Date: Sun, 21 Apr 2024 13:37:10 +0200	[thread overview]
Message-ID: <ZiT6ZlO9fECvbipo@kroah.com> (raw)

The following changes since commit 4cece764965020c22cff7665b18a012006359095:

  Linux 6.9-rc1 (2024-03-24 14:10:05 -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.9-rc5

for you to fetch changes up to 156539fd65019e8ed6b9fbac0583cf519cdbb227:

  Documentation: embargoed-hardware-issues.rst: Add myself for Power (2024-04-11 15:21:18 +0200)

----------------------------------------------------------------
Kernfs bugfix and documentation update for 6.9-rc5

Here are 2 changes for 6.9-rc5 that deal with "driver core" stuff, that
do the following:
  - sysfs reference leak fix
  - embargoed-hardware-issues.rst update for Power

Both of these have been in linux-next for over a week with no reported
issues.

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

----------------------------------------------------------------
Alan Stern (1):
      fs: sysfs: Fix reference leak in sysfs_break_active_protection()

Michael Ellerman (1):
      Documentation: embargoed-hardware-issues.rst: Add myself for Power

 Documentation/process/embargoed-hardware-issues.rst | 2 +-
 fs/sysfs/file.c                                     | 2 ++
 2 files changed, 3 insertions(+), 1 deletion(-)

             reply	other threads:[~2024-04-21 11:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-21 11:37 Greg KH [this message]
2024-04-21 17:36 ` [GIT PULL] Driver core fixes for 6.9-rc5 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=ZiT6ZlO9fECvbipo@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 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.