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:17:02 +0200 [thread overview]
Message-ID: <560D5C7E.8080900@redhat.com> (raw)
In-Reply-To: <560D5945.5050700@redhat.com>
On 10/01/15 18:03, 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.
>
This posting follows a little bit different pattern, one that I myself
follow when posting patches for two (or more) components that must work
in sync.
Usually, a top-level blurb is manually cross-posted to all relevant
mailing lists. Then, each separate patch series is posted only to the
relevant mailing list, with its own cover letter (as usual with git),
*in response* to the manually posted blurb.
This has the following benefits:
- in mailing list archives that organize messages into threads *across*
mailing lists (like Gmane does, for example), the top-level manual
blurb is a good "root" for referencing the entire posting.
- The same is true for personal mailboxes, if a recipient is explicitly
CC'd on all of the messages.
Because the top level blurb is parent to several patch series, and those
child series can all have different version numbers (due to different
numbers of respinds), it is not always straightforward to assign a
version number to the top blurb.
Thanks
Laszlo
next prev parent reply other threads:[~2015-10-01 16:17 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 12:14 [Qemu-devel] QEMU fw_cfg DMA interface Marc Marí
2015-10-01 12:16 ` [Qemu-devel] [PATCH v4 0/7] " Marc Marí
2015-10-01 12:16 ` [Qemu-devel] [PATCH v4 1/7] fw_cfg: document fw_cfg_modify_iXX() update functions Marc Marí
2015-10-01 12:16 ` [Qemu-devel] [PATCH v4 2/7] fw_cfg DMA interface documentation Marc Marí
2015-10-01 14:41 ` Laszlo Ersek
2015-10-01 12:16 ` [Qemu-devel] [PATCH v4 3/7] Implement fw_cfg DMA interface Marc Marí
2015-10-01 14:36 ` Laszlo Ersek
2015-10-01 15:52 ` Marc Marí
2015-10-01 17:18 ` Peter Maydell
2015-10-01 19:20 ` Laszlo Ersek
2015-10-06 14:44 ` Stefan Hajnoczi
2015-10-06 14:53 ` Peter Maydell
2015-10-08 9:07 ` Stefan Hajnoczi
2015-10-08 10:01 ` Marc Marí
2015-10-06 14:54 ` Marc Marí
2015-10-01 12:16 ` [Qemu-devel] [PATCH v4 4/7] Enable fw_cfg DMA interface for ARM Marc Marí
2015-10-01 14:42 ` Laszlo Ersek
2015-10-01 12:16 ` [Qemu-devel] [PATCH v4 5/7] Enable fw_cfg DMA interface for x86 Marc Marí
2015-10-01 14:48 ` Laszlo Ersek
2015-10-01 12:16 ` [Qemu-devel] [PATCH v4 6/7] Make the kernel image in the fw_cfg DMA interface bootable Marc Marí
2015-10-01 15:25 ` Laszlo Ersek
2015-10-01 16:02 ` Kevin O'Connor
2015-10-01 16:10 ` Laszlo Ersek
2015-10-01 18:15 ` Marc Marí
2015-10-02 8:16 ` Gerd Hoffmann
2015-10-02 8:24 ` Marc Marí
2015-10-02 9:01 ` Gerd Hoffmann
2015-10-02 11:47 ` Laszlo Ersek
2015-10-02 12:07 ` Gerd Hoffmann
2015-10-02 13:25 ` Laszlo Ersek
2015-10-02 13:30 ` Laszlo Ersek
2015-10-03 0:05 ` Jordan Justen
2015-10-02 13:38 ` Kevin O'Connor
2015-10-05 9:18 ` Gerd Hoffmann
2015-10-02 8:09 ` Gerd Hoffmann
2015-10-02 13:40 ` Kevin O'Connor
2015-10-02 13:50 ` Laszlo Ersek
2015-10-02 15:24 ` Daniel P. Berrange
2015-10-05 9:26 ` Gerd Hoffmann
2015-10-01 12:16 ` [Qemu-devel] [PATCH v4 7/7] fw_cfg: Define a static signature to be returned on DMA port reads Marc Marí
2015-10-01 16:07 ` Laszlo Ersek
2015-10-01 17:02 ` Kevin O'Connor
2015-10-01 17:17 ` Laszlo Ersek
2015-10-01 13:19 ` [Qemu-devel] [PATCH v4 0/7] fw_cfg DMA interface Kevin O'Connor
2015-10-01 16:03 ` [Qemu-devel] QEMU " Eric Blake
2015-10-01 16:11 ` Eric Blake
2015-10-01 16:19 ` Laszlo Ersek
2015-10-01 16:17 ` Laszlo Ersek [this message]
2015-10-01 16:21 ` Eric Blake
2015-10-01 16:34 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2015-09-18 8:58 Marc Marí
2015-08-31 9:08 Marc Marí
2015-08-06 11:00 Marc Marí
2015-08-06 12:27 ` Stefan Hajnoczi
2015-08-06 12:37 ` Marc Marí
2015-08-06 12:40 ` Stefan Hajnoczi
2015-08-06 15:30 ` Kevin O'Connor
2015-08-06 15:53 ` Marc Marí
2015-08-07 4:30 ` Kevin O'Connor
2015-08-17 22:08 ` Gerd Hoffmann
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=560D5C7E.8080900@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).