From: Mimi Zohar <zohar@linux.ibm.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Anders Roxell <anders.roxell@linaro.org>
Cc: Zhangshaokun <zhangshaokun@hisilicon.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Roberto Sassu <roberto.sassu@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-efi <linux-efi@vger.kernel.org>,
linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 20
Date: Wed, 20 Feb 2019 07:17:31 -0500 [thread overview]
Message-ID: <1550665051.17768.27.camel@linux.ibm.com> (raw)
In-Reply-To: <CAKv+Gu8G5eWeAdCB28xa=16ANFd2he9WPSztgXYwYRkhPfpEyA@mail.gmail.com>
> Fixes for this have already been proposed, and should appear in -next shortly
>
> The EFI one is here
> https://mail.google.com/mail/u/0/#label/linux-efi/FMfcgxwBVgrQRjglPkWRqRqVclGgVDnB
>
> Not sure about the IMA one, Mimi should be able to comment ...
I've already commented on the other patch and was expecting to see a
revised patch.
Mimi
next prev parent reply other threads:[~2019-02-20 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190220184341.73bd2084@canb.auug.org.au>
[not found] ` <1114b964-8ff8-5632-64d4-e94a9160b998@hisilicon.com>
[not found] ` <20190220095252.GA9089@linux.intel.com>
2019-02-20 9:58 ` linux-next: Tree for Feb 20 Jarkko Sakkinen
2019-02-20 10:05 ` Ard Biesheuvel
2019-02-20 12:17 ` Mimi Zohar [this message]
2019-02-21 0:43 ` Zhangshaokun
2019-02-21 8:03 ` Geert Uytterhoeven
2019-02-21 8:42 ` Zhangshaokun
2019-02-21 9:12 ` Ard Biesheuvel
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=1550665051.17768.27.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=anders.roxell@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=sfr@canb.auug.org.au \
--cc=zhangshaokun@hisilicon.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).