stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org,
	Jeremy Boone <jeremy.boone@nccgroup.trust>,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH] tpm: fix potential buffer overruns caused by bit glitches on the bus
Date: Mon, 19 Mar 2018 22:24:43 +0200	[thread overview]
Message-ID: <20180319202443.GA13178@linux.intel.com> (raw)
In-Reply-To: <20180316144121.GA10223@kroah.com>

On Fri, Mar 16, 2018 at 03:41:21PM +0100, Greg KH wrote:
> On Fri, Mar 16, 2018 at 04:35:02PM +0200, Jarkko Sakkinen wrote:
> > On Fri, Mar 16, 2018 at 02:11:26PM +0100, Greg KH wrote:
> > > On Fri, Mar 16, 2018 at 01:27:26PM +0200, Jarkko Sakkinen wrote:
> > > > From: Jeremy Boone <jeremy.boone@nccgroup.trust>
> > > > 
> > > > commit c8e3e06d252155ad0e38a64a65ebb85638893025 upstream
> > > 
> > > There is no such id upstream :(
> > 
> > Oops: the correct upstream ID is 3be23274755ee85771270a23af7691dc9b3a95db
> 
> Can you please resend it with the correct one so I don't have to
> hand-edit things?
> 
> thanks,
> 
> greg k-h

Yes, sure.

/Jarkko

  reply	other threads:[~2018-03-19 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 11:27 [PATCH] tpm: fix potential buffer overruns caused by bit glitches on the bus Jarkko Sakkinen
2018-03-16 13:11 ` Greg KH
2018-03-16 14:35   ` Jarkko Sakkinen
2018-03-16 14:41     ` Greg KH
2018-03-19 20:24       ` Jarkko Sakkinen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-21  8:50 Jarkko Sakkinen

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=20180319202443.GA13178@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jeremy.boone@nccgroup.trust \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).