From: Laszlo Ersek <lersek@redhat.com>
To: "Eric Blake" <eblake@redhat.com>, "Marc Marí" <markmb@redhat.com>,
linux-kernel@vger.kernel.org, qemu-devel@nongnu.org,
seabios@seabios.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Rob Herring <rob.herring@linaro.org>, Drew <drjones@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
devicetree@vger.kernel.org, Stefan Hajnoczi <stefanha@gmail.com>,
Alexander Graf <agraf@suse.de>,
Kevin O'Connor <kevin@koconnor.net>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] QEMU fw_cfg DMA interface
Date: Thu, 1 Oct 2015 18:19:17 +0200 [thread overview]
Message-ID: <560D5D05.3070607@redhat.com> (raw)
In-Reply-To: <560D5B1B.10104@redhat.com>
On 10/01/15 18:11, Eric Blake wrote:
> On 10/01/2015 10:03 AM, Eric Blake wrote:
>> [meta-comment]
>>
>> On 10/01/2015 06:14 AM, Marc Marí wrote:
>>> Implementation of the FW CFG DMA interface.
>>
>> The subject line is missing "v4" and "0/7". Also, the cover letter is
>> missing a diffstat. That makes it harder to see from the cover letter
>> what the rest of the series is about. 'git format-patch/send-email
>> --cover-letter' does what you want; you can even 'git config
>> format.coverletter=auto' to always include a decent cover letter on any
>> multi-patch series.
>
> Oh, I see - you sent a meta-cover letter (the one I replied to in this
> subthread), and then a patch series including a cover letter (the real
> 0/7, then 1/7 and friends in-reply-to the 0/7) as a child of the
> meta-cover. It's still a bit awkward for tools that expect the 0/7 as
> the start of the thread,
Yep, the pattern I just described doesn't consider those tools. Is that
a bad problem? Maybe the pattern is not so clever then. :)
(I'm allowed to say bad things about it, because I "invented" it
"independently". :))
> and part of my confusion was caused by
> out-of-order mail delivery due to the nongnu.org mail server still
> recovering from its mail delays.
>
Right, those delays are not helping.
Thanks
Laszlo
next prev parent reply other threads:[~2015-10-01 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 12:14 QEMU fw_cfg DMA interface Marc Marí
[not found] ` <1443701677-13629-1-git-send-email-markmb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-01 12:15 ` [PATCH v4] QEMU fw_cfg DMA interface documentation Marc Marí
[not found] ` <1443701732-13696-1-git-send-email-markmb-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-05 8:20 ` Stefan Hajnoczi
2015-10-05 10:06 ` Marc Marí
2015-10-05 10:11 ` Stefan Hajnoczi
2015-10-01 16:03 ` [Qemu-devel] QEMU fw_cfg DMA interface Eric Blake
[not found] ` <560D5945.5050700-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-01 16:11 ` Eric Blake
2015-10-01 16:19 ` Laszlo Ersek [this message]
2015-10-01 16:17 ` Laszlo Ersek
[not found] ` <560D5C7E.8080900-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-01 16:21 ` Eric Blake
2015-10-01 16:34 ` Laszlo Ersek
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=560D5D05.3070607@redhat.com \
--to=lersek@redhat.com \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=drjones@redhat.com \
--cc=eblake@redhat.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=markmb@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rob.herring@linaro.org \
--cc=seabios@seabios.org \
--cc=stefanha@gmail.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).