From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v1] efi: Don't use knowledge about efi_guid_t internals
Date: Thu, 26 Aug 2021 18:08:40 +0300 [thread overview]
Message-ID: <YSeueHLVPsfCO0ah@smile.fi.intel.com> (raw)
In-Reply-To: <CAMj1kXFHG4G+KCv4KaL6XYtAPs99bsQ-0fik8oKv4GWDw2+GJg@mail.gmail.com>
On Thu, Jun 10, 2021 at 05:05:55PM +0200, Ard Biesheuvel wrote:
> On Mon, 7 Jun 2021 at 19:11, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Tue, Feb 09, 2021 at 05:51:45PM +0100, Ard Biesheuvel wrote:
> > > On Tue, 9 Feb 2021 at 17:45, Andy Shevchenko
> > > <andriy.shevchenko@linux.intel.com> wrote:
> > > >
> > > > When print GUIDs supply pointer to the efi_guid_t (guid_t) type rather
> > > > its internal members.
> > > >
> > > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > >
> > > Acked-by: Ard Biesheuvel <ardb@kernel.org>
> >
> > Thanks!
> >
> > Can we get this applied, please?
>
> Apologies, this one slipped behind the desk.
Do I need to resend it?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-08-26 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 16:45 [PATCH v1] efi: Don't use knowledge about efi_guid_t internals Andy Shevchenko
2021-02-09 16:51 ` Ard Biesheuvel
2021-06-07 17:11 ` Andy Shevchenko
2021-06-10 15:05 ` Ard Biesheuvel
2021-08-26 15:08 ` Andy Shevchenko [this message]
2021-08-26 16:37 ` Ard Biesheuvel
2021-08-26 20:27 ` Serge E. Hallyn
-- strict thread matches above, loose matches on Subject: below --
2020-10-15 11:50 Andy Shevchenko
2021-01-02 21:36 ` Andy Shevchenko
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=YSeueHLVPsfCO0ah@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=ardb@kernel.org \
--cc=jmorris@namei.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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;
as well as URLs for NNTP newsgroup(s).