From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] pstore update for v4.12-rc2
Date: Tue, 16 May 2017 11:54:48 -0700 [thread overview]
Message-ID: <20170516185448.GA87595@beast> (raw)
Hi,
Please pull this pstore fix for v4.12-rc2.
Thanks!
-Kees
The following changes since commit 3a7d2fd16c57a1ef47dc2891171514231c9c7c6e:
pstore: Solve lockdep warning by moving inode locks (2017-04-27 20:35:34 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v4.12-rc2
for you to fetch changes up to 6f61dd3aa35179043f1fcdb0965c5d56278ab724:
efi-pstore: Fix read iter after pstore API refactor (2017-05-16 11:46:49 -0700)
----------------------------------------------------------------
- fix bad EFI vars iterator usage
----------------------------------------------------------------
Kees Cook (1):
efi-pstore: Fix read iter after pstore API refactor
drivers/firmware/efi/efi-pstore.c | 12 +++---------
1 file changed, 3 insertions(+), 9 deletions(-)
--
Kees Cook
Pixel Security
reply other threads:[~2017-05-16 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170516185448.GA87595@beast \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--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