From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: coreyb@linux.vnet.ibm.com,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] tpm: Simplify creation of cancel path
Date: Thu, 18 Apr 2013 13:38:03 -0400 [thread overview]
Message-ID: <51702F7B.2060204@linux.vnet.ibm.com> (raw)
In-Reply-To: <87haj6e3xi.fsf@codemonkey.ws>
On 04/16/2013 02:16 PM, Anthony Liguori wrote:
> Stefan Berger <stefanb@linux.vnet.ibm.com> writes:
>
>> Simplify the creation of the cancel path given the TPM's device path.
>> Given the path /dev/tpm0 build the path /sys/class/misc/tpm0/device/cancel.
>>
>> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
> No longer applies. Had you sent with git-send-patch, git am --3way
> would have figured it out. Please use git-send-patch in the future.
I reposted it.
http://lists.gnu.org/archive/html/qemu-devel/2013-04/msg03330.html
Stefan
prev parent reply other threads:[~2013-04-18 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 21:08 [Qemu-devel] [PATCH] tpm: Simplify creation of cancel path Stefan Berger
2013-04-15 21:13 ` Eric Blake
2013-04-16 18:16 ` Anthony Liguori
2013-04-18 17:38 ` Stefan Berger [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=51702F7B.2060204@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=coreyb@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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).