mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Kees Cook <kees@kernel.org>, Tony Luck <tony.luck@intel.com>
Cc: linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: pstore: Remove L: entry
Date: Fri, 16 Jan 2026 19:26:01 -0300	[thread overview]
Message-ID: <0ebc75a7-b804-05d0-383f-9d542b14824e@igalia.com> (raw)
In-Reply-To: <20260116005631.work.387-kees@kernel.org>

On 15/01/2026 21:56, Kees Cook wrote:
> A lot of SoC series end up getting CCed to the hardening list due to
> their mention of "pstore" in device tree or similar, and this noise isn't
> worth making sure I don't lose pstore patches by having them show up in
> the hardening patchwork. ;) I can use better email filters instead!
> 
> Signed-off-by: Kees Cook <kees@kernel.org>
> ---
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: Guilherme G. Piccoli <gpiccoli@igalia.com>
> ---
>  MAINTAINERS | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index dc731d37c8fe..02c2cb7accb8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -20961,7 +20961,6 @@ PSTORE FILESYSTEM
>  M:	Kees Cook <kees@kernel.org>
>  R:	Tony Luck <tony.luck@intel.com>
>  R:	Guilherme G. Piccoli <gpiccoli@igalia.com>
> -L:	linux-hardening@vger.kernel.org
>  S:	Supported
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore
>  F:	Documentation/admin-guide/pstore-blk.rst


Just want to explicitly thank you for that! Indeed, I think this might
improve a lot the signal-to-noise of pstore patches =)

      reply	other threads:[~2026-01-16 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16  0:56 Kees Cook
2026-01-16 22:26 ` 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=0ebc75a7-b804-05d0-383f-9d542b14824e@igalia.com \
    --to=gpiccoli@igalia.com \
    --cc=kees@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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®