From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Guenter Roeck <groeck@chromium.org>,
Joel Fernandes <joel@joelfernandes.org>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Subject: [GIT PULL] pstore updates for v4.20-rc1
Date: Mon, 22 Oct 2018 07:24:40 -0700 [thread overview]
Message-ID: <20181022142440.GA10225@beast> (raw)
Hi Linus,
Please pull these pstore changes for v4.20-rc1.
Thanks!
-Kees
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/pstore-v4.20-rc1
for you to fetch changes up to 1227daa43bce1318ff6fb54e6cd862b4f60245c7:
pstore/ram: Clarify resource reservation labels (2018-10-22 07:11:58 -0700)
----------------------------------------------------------------
pstore improvements:
- refactor init to happen as early as possible again (Joel Fernandes)
- improve resource reservation names
----------------------------------------------------------------
Joel Fernandes (Google) (1):
pstore: Allocate compression during late_initcall()
Kees Cook (3):
pstore: Centralize init/exit routines
pstore: Refactor compression initialization
pstore/ram: Clarify resource reservation labels
fs/pstore/inode.c | 11 ++-----
fs/pstore/internal.h | 5 ++--
fs/pstore/platform.c | 75 ++++++++++++++++++++++++++++++++++++++--------
fs/pstore/ram.c | 18 ++++++++---
fs/pstore/ram_core.c | 11 ++++---
include/linux/pstore_ram.h | 3 +-
6 files changed, 90 insertions(+), 33 deletions(-)
--
Kees Cook
Pixel Security
next reply other threads:[~2018-10-22 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 14:24 Kees Cook [this message]
2018-10-24 13:47 ` [GIT PULL] pstore updates for v4.20-rc1 Linus Torvalds
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=20181022142440.GA10225@beast \
--to=keescook@chromium.org \
--cc=groeck@chromium.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saiprakash.ranjan@codeaurora.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 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.