linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
	linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
	Wilck@intel.com, Martin <martin.wilck@ts.fujitsu.com>,
	Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Subject: Re: [GIT PULL] remaining tpmdd fixes for Linux 4.5
Date: Fri, 26 Feb 2016 11:00:19 +0200	[thread overview]
Message-ID: <20160226090019.GA2720@intel.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1602261857040.28734@namei.org>

On Fri, Feb 26, 2016 at 06:57:49PM +1100, James Morris wrote:
> On Mon, 22 Feb 2016, Jarkko Sakkinen wrote:
> 
> > Do you want me to send a pull request containing a fix for the build
> > warning or reverting the whole commit? My call would be to apply the
> > fix because this commit has been tested both TPM 1.2 by Martin and
> > with TPM 2.0 by me and things have worked well.
> > 
> 
> Send me a pull request just for the fix.
> 
> I won't be pushing these changes to Linus for 4.5, they'll have to wait 
> until the 4.6.

OK

> -- 
> James Morris
> <jmorris@namei.org>

/Jarkko

      reply	other threads:[~2016-02-26  9:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20  8:17 [GIT PULL] remaining tpmdd fixes for Linux 4.5 Jarkko Sakkinen
2016-02-22  1:56 ` James Morris
2016-02-22 14:50   ` Jarkko Sakkinen
2016-02-22 17:52     ` Jason Gunthorpe
2016-02-22 19:08       ` Jarkko Sakkinen
2016-02-22 19:11         ` Jason Gunthorpe
2016-02-22 21:23           ` Jarkko Sakkinen
2016-02-25 17:30     ` [tpmdd-devel] " Jerry Snitselaar
2016-02-26  3:38       ` James Morris
2016-02-26  9:48         ` Jarkko Sakkinen
2016-02-26  7:57     ` James Morris
2016-02-26  9:00       ` Jarkko Sakkinen [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=20160226090019.GA2720@intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=Wilck@intel.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=martin.wilck@ts.fujitsu.com \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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).