From: Eric Blake <eblake@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, marcandre.lureau@redhat.com
Cc: famz@redhat.com, ehabkost@redhat.com, mst@redhat.com,
armbru@redhat.com, pbonzini@redhat.com, marcel@redhat.com,
imammedo@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v3] tpm: add CRB device
Date: Mon, 29 Jan 2018 08:24:36 -0600 [thread overview]
Message-ID: <b60c4753-378f-f739-c30b-ac2c590ccacf@redhat.com> (raw)
In-Reply-To: <4e2b09bd-c08f-ef6a-948f-a488051effcd@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
On 01/28/2018 07:38 AM, Stefan Berger wrote:
> On 01/26/2018 08:19 AM, no-reply@patchew.org wrote:
>> Hi,
>>
>> This series failed build test on s390x host. Please find the details
>> below.
>
> We can ignore this and the other emails' errors since the patch's
> dependencies are in my tpm-next tree.
The cover letter said this:
> The patch is based on stefanb/tpm-next git branch.
But patchew doesn't recognize that spelling. The better way to get
patchew to not spit out those warnings in the first place is to add this
to your cover letter:
Based-on: <1516992568-3139-1-git-send-email-stefanb@linux.vnet.ibm.com>
(Merge tpm 2018/01/26)
(or whatever better message id is relevant)
Hmm, I'm also noticing that MAINTAINERS lacks a T: entry under TPM that
says where the stefanb/tpm-next git branch can be downloaded; the
above-mentioned message id mentions
git://github.com/stefanberger/qemu-tpm.git. I don't know if patchew
recognizes a git repo+branch name as an alternative to message-id for
the Based-on tag (for that matter, a maintainer branch might not always
have stable commit ids, which could make life interesting if patchew
tests against one version then the maintainer changes by rebase and the
series would then break)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2018-01-29 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 12:03 [Qemu-devel] [PATCH v3] tpm: add CRB device Marc-André Lureau
2018-01-26 12:09 ` Marc-Andre Lureau
2018-01-26 13:19 ` no-reply
2018-01-28 13:38 ` Stefan Berger
2018-01-29 14:24 ` Eric Blake [this message]
2018-01-26 13:23 ` no-reply
2018-01-26 13:27 ` no-reply
2018-01-26 13:27 ` no-reply
2018-01-26 13:30 ` no-reply
2018-01-26 18:50 ` Stefan Berger
2018-01-29 16:24 ` Igor Mammedov
2018-01-29 16:50 ` Stefan Berger
2018-01-30 8:35 ` Igor Mammedov
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=b60c4753-378f-f739-c30b-ac2c590ccacf@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=famz@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanb@linux.vnet.ibm.com \
/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).