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-rc5
Date: Sun, 2 Apr 2023 16:50:15 +0200 [thread overview]
Message-ID: <ZCmWJ_E1FKCf3aEW@kroah.com> (raw)
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -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-rc5
for you to fetch changes up to 5c2712387d4850e0b64121d5fd3e6c4e84ea3266:
cacheinfo: Fix LLC is not exported through sysfs (2023-03-29 12:04:10 +0200)
----------------------------------------------------------------
Driver core fixes for 6.3-rc5
Here are 3 small changes for 6.3-rc5 semi-related to driver core stuff:
- documentation update where we move the security_bugs file to a more
relevant location.
- mdt/spi-nor debugfs memory leak fix that's been floating around for
a long time and acked by the maintainer
- cacheinfo bugfix for a regression in 6.3-rc1
All have been in linux-next with no reported problems.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Greg Kroah-Hartman (1):
mtd: spi-nor: fix memory leak when using debugfs_lookup()
Vegard Nossum (1):
Documentation/security-bugs: move from admin-guide/ to process/
Yicong Yang (1):
cacheinfo: Fix LLC is not exported through sysfs
Documentation/admin-guide/index.rst | 1 -
Documentation/admin-guide/reporting-issues.rst | 4 ++--
Documentation/process/howto.rst | 2 +-
Documentation/process/index.rst | 9 ++++++++-
Documentation/process/researcher-guidelines.rst | 2 +-
Documentation/{admin-guide => process}/security-bugs.rst | 0
Documentation/process/stable-kernel-rules.rst | 2 +-
Documentation/process/submitting-patches.rst | 2 +-
.../translations/it_IT/admin-guide/security-bugs.rst | 2 +-
.../translations/it_IT/process/submitting-patches.rst | 2 +-
Documentation/translations/ja_JP/howto.rst | 2 +-
Documentation/translations/ko_KR/howto.rst | 2 +-
Documentation/translations/sp_SP/howto.rst | 2 +-
.../translations/sp_SP/process/submitting-patches.rst | 2 +-
.../translations/zh_CN/admin-guide/security-bugs.rst | 2 +-
Documentation/translations/zh_CN/process/howto.rst | 2 +-
.../translations/zh_TW/admin-guide/security-bugs.rst | 2 +-
Documentation/translations/zh_TW/process/howto.rst | 2 +-
MAINTAINERS | 4 ++--
drivers/base/cacheinfo.c | 16 +++++++++++-----
drivers/mtd/spi-nor/core.c | 14 +++++++++++++-
drivers/mtd/spi-nor/core.h | 2 ++
drivers/mtd/spi-nor/debugfs.c | 11 ++++++++---
23 files changed, 60 insertions(+), 29 deletions(-)
rename Documentation/{admin-guide => process}/security-bugs.rst (100%)
next reply other threads:[~2023-04-02 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 14:50 Greg KH [this message]
2023-04-02 18:02 ` [GIT PULL] Driver core fixes for 6.3-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=ZCmWJ_E1FKCf3aEW@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