From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Jann Horn <jannh@google.com>,
Kees Cook <keescook@chromium.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Vincent Whitchurch <vincent.whitchurch@axis.com>
Subject: [GIT PULL] pstore updates for v5.18-rc1
Date: Mon, 21 Mar 2022 07:47:53 -0700 [thread overview]
Message-ID: <202203210747.C40221E63F@keescook> (raw)
Hi Linus,
Please pull these two pstore updates for v5.18-rc1.
Thanks!
-Kees
The following changes since commit 26291c54e111ff6ba87a164d85d4a4e134b7315c:
Linux 5.17-rc2 (2022-01-30 15:37:07 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v5.18-rc1
for you to fetch changes up to 8126b1c73108bc691f5643df19071a59a69d0bc6:
pstore: Don't use semaphores in always-atomic-context code (2022-03-15 11:08:23 -0700)
----------------------------------------------------------------
pstore updates for v5.18-rc1
- Don't use semaphores in always-atomic-context code (Jann Horn)
- Add "ECC:" prefix to ECC messages (Vincent Whitchurch)
----------------------------------------------------------------
Jann Horn (1):
pstore: Don't use semaphores in always-atomic-context code
Vincent Whitchurch (1):
pstore: Add prefix to ECC messages
drivers/firmware/efi/efi-pstore.c | 2 +-
fs/pstore/platform.c | 38 ++++++++++++++++++--------------------
fs/pstore/ram_core.c | 4 ++--
include/linux/pstore.h | 6 +++---
4 files changed, 24 insertions(+), 26 deletions(-)
--
Kees Cook
next reply other threads:[~2022-03-21 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 14:47 Kees Cook [this message]
2022-03-22 3:06 ` 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=202203210747.C40221E63F@keescook \
--to=keescook@chromium.org \
--cc=bigeasy@linutronix.de \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.whitchurch@axis.com \
/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
all inboxes | Powered by JetHome®