From: Andrew Morton <akpm@linux-foundation.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: James Morris <jmorris@namei.org>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
srajiv@linux.vnet.ibm.com,
Debora Velarde <debora@linux.vnet.ibm.com>,
Marcel Selhorst <m.selhorst@sirrix.com>,
Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH] TPM: Fixup pcrs sysfs file
Date: Mon, 14 Sep 2009 00:11:36 -0700 [thread overview]
Message-ID: <20090914001136.f1fd580a.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090914062520.GB23467@obsidianresearch.com>
On Mon, 14 Sep 2009 00:25:20 -0600 Jason Gunthorpe <jgunthorpe@obsidianresearch.com> wrote:
> On Mon, Sep 14, 2009 at 12:36:39PM +1000, James Morris wrote:
> > On Thu, 3 Sep 2009, Jason Gunthorpe wrote:
>
> > > > That sounds like a fairly serious bug, and this looks like a 2.6.31
> > > > patch.
> >
> > Any comments from the maintainers on this patch?
>
> FWIW, I didn't mention in the patch emails, but all the patches I sent
> fix regressions that have been introduced in the past couple years by
> clean up patches that never tested the code paths they alter.
>
> What becomes of patches that end up in the mm tree? Do they still
> route through you for mainline inclusion?
I'll be sending tpm patches to James henceforth. I presently have
tpm-fixup-pcrs-sysfs-file.patch
tpm-fixup-pcrs-sysfs-file-update.patch
tpm-fix-up-pubek-sysfs-file.patch
next prev parent reply other threads:[~2009-09-14 7:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 3:16 Jason Gunthorpe
2009-09-03 23:52 ` Andrew Morton
2009-09-04 1:28 ` Jason Gunthorpe
2009-09-14 2:36 ` James Morris
2009-09-14 6:25 ` Jason Gunthorpe
2009-09-14 7:11 ` Andrew Morton [this message]
2009-09-14 17:45 ` Rajiv Andrade
2009-09-14 17:52 ` Rajiv Andrade
2009-09-14 18:00 ` Jason Gunthorpe
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=20090914001136.f1fd580a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=debora@linux.vnet.ibm.com \
--cc=jbeulich@novell.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.selhorst@sirrix.com \
--cc=srajiv@linux.vnet.ibm.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
Powered by JetHome