From: James Morris <jmorris@namei.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [GIT PULL] tpmdd fixes for 4.16
Date: Tue, 27 Feb 2018 10:33:37 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1802271033190.9747@namei.org> (raw)
In-Reply-To: <1519674546.3941.2.camel@HansenPartnership.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: multipart/mixed; boundary="1665246916-613390738-1519688018=:9747", Size: 627 bytes --]
On Mon, 26 Feb 2018, James Bottomley wrote:
> On Tue, 2018-02-27 at 05:52 +1100, James Morris wrote:
> > On Mon, 26 Feb 2018, Jarkko Sakkinen wrote:
> >
> > >
> > > Hi
> > >
> > > Here is a batch of critical fixes for 4.16.
> > >
> >
> > Do you have CVEs for these? If so, please include them in the commit
> > messages.
>
> Heh, well, I suppose from this everyone now knows they're fixes for
> vulnerabilities. The CVE doesn't usually show up until after the
> embargo is released, so we don't have one yet.
Anyone with half a brain can read Linus' -rc commits and work it out.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2018-02-26 23:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 12:41 [GIT PULL] tpmdd fixes for 4.16 Jarkko Sakkinen
2018-02-26 18:52 ` James Morris
2018-02-26 19:49 ` James Bottomley
2018-02-26 23:33 ` James Morris [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=alpine.LRH.2.21.1802271033190.9747@namei.org \
--to=jmorris@namei.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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