From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-hardening@vger.kernel.org,
Anton Vorontsov <anton@enomsg.org>,
Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>,
Paramjit Oberoi <pso@chromium.org>,
Ard Biesheuvel <ardb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] MAINTAINERS: Update pstore maintainers
Date: Thu, 17 Nov 2022 19:05:05 -0300 [thread overview]
Message-ID: <34c3a141-ca0a-d4db-15de-399f4948518d@igalia.com> (raw)
In-Reply-To: <202211171359.232C769E3A@keescook>
On 17/11/2022 19:01, Kees Cook wrote:
> [...]
>> PSTORE FILESYSTEM
>> M: Kees Cook <keescook@chromium.org>
>> [...]
>> F: include/linux/pstore*
>> K: \b(pstore|ramoops) <------
>>
>> Should this be kept? Maybe only the ramoops entry could be removed?
>
> I would like to keep it -- if something mentions pstore and ramoops, I'd
> like to see it. I can't review all of it, but I'd like it to at least
> show up in my inbox. :)
>
Totally fine by me, was curious and now I understand this is not legacy,
but something of your interest indeed.
Thanks for the prompt response!
Cheers,
Guilherme
prev parent reply other threads:[~2022-11-17 22:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 20:01 [PATCH 0/5] Move internal definitions out of kernel-wide include Kees Cook
2022-10-11 20:01 ` [PATCH 1/5] pstore/ram: Consolidate kfree() paths Kees Cook
2022-10-12 19:43 ` Guilherme G. Piccoli
2022-10-11 20:01 ` [PATCH 2/5] pstore/ram: Move pmsg init earlier Kees Cook
2022-10-12 19:45 ` Guilherme G. Piccoli
2022-10-11 20:01 ` [PATCH 3/5] pstore/ram: Move internal definitions out of kernel-wide include Kees Cook
2022-10-12 19:46 ` Guilherme G. Piccoli
2022-10-12 21:51 ` Kees Cook
2022-10-11 20:01 ` [PATCH 4/5] pstore/ram: Set freed addresses to NULL Kees Cook
2022-10-12 19:44 ` Guilherme G. Piccoli
2022-10-11 20:01 ` [PATCH 5/5] MAINTAINERS: Update pstore maintainers Kees Cook
2022-10-11 20:26 ` Colin Cross
2022-10-11 20:35 ` Guilherme G. Piccoli
2022-10-11 22:20 ` Kees Cook
2022-10-12 15:15 ` Guilherme G. Piccoli
2022-11-16 15:42 ` Guilherme G. Piccoli
2022-11-17 22:01 ` Kees Cook
2022-11-17 22:05 ` Guilherme G. Piccoli [this message]
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=34c3a141-ca0a-d4db-15de-399f4948518d@igalia.com \
--to=gpiccoli@igalia.com \
--cc=anton@enomsg.org \
--cc=ardb@kernel.org \
--cc=ccross@android.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pso@chromium.org \
--cc=tony.luck@intel.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 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.