From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Kent Yoder <shpedoikal@gmail.com>
Cc: leosilva@linux.vnet.ibm.com, adlai@linux.vnet.ibm.com,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
TPM Device Driver List <tpmdd-devel@lists.sourceforge.net>,
Ian.Campbell@citrix.com, Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [tpmdd-devel] [PATCH v2] drivers/tpm: add xen tpmfront interface
Date: Fri, 24 May 2013 10:37:59 -0400 [thread overview]
Message-ID: <20130524143759.GA4404@phenom.dumpdata.com> (raw)
In-Reply-To: <CAM0nabFO_tTqsX5c7Q-Z14CbRnqo9m11f__xkfzt6c8M026D_A@mail.gmail.com>
On Wed, May 22, 2013 at 05:12:24PM -0500, Kent Yoder wrote:
> On Wed, May 22, 2013 at 3:57 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> > On Wed, May 22, 2013 at 02:47:01PM -0500, Kent Yoder wrote:
> >> >> + notify_remote_via_evtchn(priv->evtchn);
> >> >> +
> >> >> + ordinal = be32_to_cpu(*((__be32 *) (buf + 6)));
> >> >
> >> > Um, + 6? Why? Is there an #define for that magic constant?
> >> > Should this value be read before you do the wait_for_tpm_stat stuff?
> >>
> >> This is hardcoded to 6 even in tpm.c. Time for a #define...
> >>
> >> > Otherwise it looks OK to me. Should this go through me or Kent?
> >> > And if so, is Kent waiting for my feedback?
> >>
> >> My comments were minor -- I was expecting feedback on your earlier
> >> comments before merging. I think this should go through the tpmdd
> >> maintainer if its going to live in drivers/char/tpm though.
> >
> > That is you I thought?
> >
> > konrad@phenom:~/mm$ scripts/get_maintainer.pl -f drivers/char/tpm
> > Kent Yoder <key@linux.vnet.ibm.com> (maintainer:TPM DEVICE DRIVER)
> > Rajiv Andrade <mail@srajiv.net> (maintainer:TPM DEVICE DRIVER)
> > Marcel Selhorst <tpmdd@selhorst.net> (maintainer:TPM DEVICE DRIVER)
> > Sirrix AG <tpmdd@sirrix.com> (maintainer:TPM DEVICE DRIVER)
> > tpmdd-devel@lists.sourceforge.net (moderated list:TPM DEVICE DRIVER)
> > linux-kernel@vger.kernel.org (open list)
>
> That was me until today. :-) But I didn't see the response your comments yet.
Congratulations to you on a move to a new job!! Can you say what it is?
I am sure Daniel will post a patch shortly, and will CC everybody that get_maintainer.pl
finds.
next prev parent reply other threads:[~2013-05-24 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 14:56 [PATCH v2] drivers/tpm: add xen tpmfront interface Daniel De Graaf
2013-04-19 20:08 ` [tpmdd-devel] " Kent Yoder
2013-05-22 19:15 ` Konrad Rzeszutek Wilk
2013-05-22 19:47 ` [tpmdd-devel] " Kent Yoder
2013-05-22 20:57 ` Konrad Rzeszutek Wilk
2013-05-22 22:12 ` Kent Yoder
2013-05-24 14:37 ` Konrad Rzeszutek Wilk [this message]
2013-05-28 14:16 ` Kent Yoder
2013-05-28 15:40 ` Daniel De Graaf
2013-05-28 21:58 ` [tpmdd-devel] " Peter Hüwe
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=20130524143759.GA4404@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=adlai@linux.vnet.ibm.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=leosilva@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shpedoikal@gmail.com \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=xen-devel@lists.xen.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).