From: "Hon Ching (Vicky) Lo" <honclo@linux.vnet.ibm.com>
To: Ashley Lai <ashley@ashleylai.com>
Cc: tpmdd-devel@lists.sourceforge.net,
Peter Huewe <PeterHuewe@gmx.de>, Vicky Lo <honclo2014@gmail.com>,
linux-kernel@vger.kernel.org,
Joy Latten <jmlatten@linux.vnet.ibm.com>
Subject: Re: [PATCH v2 1/2] vTPM: support little endian guests
Date: Wed, 17 Jun 2015 17:18:56 -0400 [thread overview]
Message-ID: <1434575936.5335.2.camel@vtpm2014.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1506161959240.23568@ant>
Hi Ashley,
Ah, good catch. I think I can only join the first two lines (where the
assignments are) and will have to leave the rest splitted. I'll resubmit
this one soon.
Thanks for the review!
Vicky
On Tue, 2015-06-16 at 20:17 -0500, Ashley Lai wrote:
> Just a small comment otherwise it looks good.
>
> On Tue, 9 Jun 2015, Hon Ching(Vicky) Lo wrote:
> > case NONHOST_INFO:
> > - name = tcpa_event_type_strings[event->event_type];
> > + name =
> > + tcpa_event_type_strings[do_endian_conversion
> > + (event->event_type)];
> Not being picky but if it does not exceed 80 characters it looks better
> to join the line above.
> name = tcpa_event_type_strings[do_endian_conversion
> (event->event_type)];
>
> > case POST_CONTENTS:
> > - name = tcpa_pc_event_id_strings[pc_event->event_id];
> > + name =
> > + tcpa_pc_event_id_strings[do_endian_conversion
> > + (pc_event->event_id)];
> Same as above.
>
> Thanks,
> --Ashley Lai
>
prev parent reply other threads:[~2015-06-17 21:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 1:54 [PATCH v2 1/2] vTPM: support little endian guests Hon Ching(Vicky) Lo
2015-06-10 1:54 ` [PATCH v2 2/2] TPM: remove unnecessary little endian conversion Hon Ching(Vicky) Lo
2015-06-17 1:20 ` Ashley Lai
2015-06-17 1:17 ` [PATCH v2 1/2] vTPM: support little endian guests Ashley Lai
2015-06-17 21:18 ` Hon Ching (Vicky) Lo [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=1434575936.5335.2.camel@vtpm2014.ibm.com \
--to=honclo@linux.vnet.ibm.com \
--cc=PeterHuewe@gmx.de \
--cc=ashley@ashleylai.com \
--cc=honclo2014@gmail.com \
--cc=jmlatten@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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