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.1-rc6
Date: Fri, 18 Nov 2022 10:28:29 +0100 [thread overview]
Message-ID: <Y3dQPc4c0pOW6KfG@kroah.com> (raw)
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -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.1-rc6
for you to fetch changes up to 1edfe4ea16ca2c9e91ec6cecd446b13636724e4f:
kernfs: Fix spurious lockdep warning in kernfs_find_and_get_node_by_id() (2022-11-10 19:03:42 +0100)
----------------------------------------------------------------
Driver core fixes for 6.1-rc6
Here are 2 small driver core fixes for 6.1-rc6:
- utsname fix, this one should already be in your tree as it
came from a different tree earlier.
- kernfs bugfix for a much reported syzbot report that seems to
keep getting triggered.
Both of these have been in linux-next for a while with no reported
issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Petr Vorel (1):
kernel/utsname_sysctl.c: Add missing enum uts_proc value
Tejun Heo (1):
kernfs: Fix spurious lockdep warning in kernfs_find_and_get_node_by_id()
fs/kernfs/dir.c | 14 ++++++++++++--
include/linux/utsname.h | 1 +
2 files changed, 13 insertions(+), 2 deletions(-)
next reply other threads:[~2022-11-18 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 9:28 Greg KH [this message]
2022-11-18 20:21 ` [GIT PULL] Driver core fixes for 6.1-rc6 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=Y3dQPc4c0pOW6KfG@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