[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMj1kXGg9moz0Fg+wFYg2GjLD2gW1RGmQqT3mu+cNi0KuYyAqA@mail.gmail.com>
Date: Fri, 7 Oct 2022 10:47:32 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: "Guilherme G. Piccoli" <gpiccoli@...lia.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
kernel-dev@...lia.com, kernel@...ccoli.net, anton@...msg.org,
ccross@...roid.com, tony.luck@...el.com, linux-efi@...r.kernel.org
Subject: Re: [PATCH 7/8] efi: pstore: Follow convention for the efi-pstore
backend name
On Fri, 7 Oct 2022 at 01:16, Kees Cook <keescook@...omium.org> wrote:
>
> On Thu, Oct 06, 2022 at 07:42:11PM -0300, Guilherme G. Piccoli wrote:
> > For some reason, the efi-pstore backend name (exposed through the
> > pstore infrastructure) is hardcoded as "efi", whereas all the other
> > backends follow a kind of convention in using the module name.
> >
> > Let's do it here as well, to make user's life easier (they might
> > use this info for unloading the module backend, for example).
> >
> > Cc: Ard Biesheuvel <ardb@...nel.org>
> > Signed-off-by: Guilherme G. Piccoli <gpiccoli@...lia.com>
>
> Looks fine to me. Ard, if you don't object, I can carry this in the
> pstore tree.
>
Acked-by: Ard Biesheuvel <ardb@...nel.org>
Powered by blists - more mailing lists