From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Ashley Lai <adlai@linux.vnet.ibm.com>
Cc: Peter Huewe <PeterHuewe@gmx.de>, Rajiv Andrade <mail@srajiv.net>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Re: [tpmdd-devel] [PATCH] tpm: MAINTAINERS: Add myself as tpm maintainer
Date: Wed, 23 Oct 2013 22:16:20 -0600 [thread overview]
Message-ID: <20131024041620.GA32346@obsidianresearch.com> (raw)
In-Reply-To: <1382587279.5587.9.camel@fishsauce>
On Wed, Oct 23, 2013 at 11:01:19PM -0500, Ashley Lai wrote:
>
> > Agreed, there are still lots of patches to go before the subsystem
> > meets the current kernel standard..
> >
> > Speaking of which, has anyone looked at the rest of my series?? Shall
> > I repost it?
>
> Jason,
> Are you referring to the for-tpm branch on github?
> https://github.com/jgunthorpe/linux/commits/for-tpm
> Peter already submitted most of the patches to James from this branch.
> Let us know which series need to be review.
All of those patches in for-tpm have gone to James.
However, the original series I posted included 5 additional patches
that have received no comment, available on:
https://github.com/jgunthorpe/linux/commits/tpm-devel
Jason Gunthorpe:
tpm: Pull everything related to /dev/tpmX into tpm-dev.c
tpm: Pull everything related to sysfs into tpm-sysfs.c
tpm: Create a tpm_class_ops structure and use it in the drivers
tpm: Use the ops structure instead of a copy in tpm_vendor_specific
tpm: Make tpm-dev allocate a per-file structure
These would have been posted as patch numbers 8 through 13 in the
original series.
I think what happened is at this point in the series module compile
broke. That is fixed now in the for-james pull, so the rest of the
series should be looked at.
Peter's checkpatch clean up will create some minor conflicts, so I
should probably resend the lot after rebasing it.
Jason
next prev parent reply other threads:[~2013-10-24 4:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 17:36 [PATCH] tpm: MAINTAINERS: Add myself as tpm maintainer Peter Huewe
2013-10-22 17:55 ` [tpmdd-devel] " Joel Schopp
2013-10-22 19:33 ` Aw: " Peter Huewe
2013-10-22 19:42 ` Ashley D Lai
2013-10-22 19:48 ` Luigi Semenzato
2013-10-22 19:59 ` Aw: " Joel Schopp
2013-10-22 20:52 ` Jason Gunthorpe
2013-10-23 19:41 ` Rajiv Andrade
2013-10-23 23:10 ` Aw: " Peter Huewe
2013-10-24 3:27 ` Jason Gunthorpe
2013-10-24 4:01 ` Ashley Lai
2013-10-24 4:16 ` Jason Gunthorpe [this message]
2013-10-24 4:28 ` Joel Schopp
2013-10-24 7:46 ` Aw: " Peter Huewe
2013-10-29 1:36 ` Rajiv Andrade
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=20131024041620.GA32346@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=PeterHuewe@gmx.de \
--cc=adlai@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@srajiv.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.