From: "Andreas Färber" <afaerber@suse.de>
To: Peter Chubb <peter.chubb@nicta.com.au>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [patch V5 0/5] i.MX31 support
Date: Tue, 03 Apr 2012 11:45:20 +0200 [thread overview]
Message-ID: <4F7AC6B0.3060002@suse.de> (raw)
In-Reply-To: <20120403015515.871951738@nicta.com.au>
Peter,
Am 03.04.2012 03:55, schrieb Peter Chubb:
> This is the fifth round of patches for preliminary Freescale i.MX31
> support.
If you resend this, it would be nice to shorten the subjects, so that
the interesting part is not hidden in the back. First one's fine, then
for example:
i.MX31: Clock Control Module
i.MX31: Timers
i.MX31: AVIC
i.MX31: KZM-ARM11-01 evaluation board
Freescale is mentioned further down in most commit messages (in varying
spellings fwiw - freescale.com has it as "Freescale").
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-04-03 9:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 1:55 [Qemu-devel] [patch V5 0/5] i.MX31 support Peter Chubb
2012-04-03 1:55 ` [Qemu-devel] [patch V5 1/5] i.MX UART support Peter Chubb
2012-04-03 1:55 ` [Qemu-devel] [patch V5 2/5] Implement i.MX31 Clock Control Module Peter Chubb
2012-04-05 17:31 ` Peter Maydell
2012-04-03 1:55 ` [Qemu-devel] [patch V5 3/5] FreeSCALE i.MX31 support: Timers Peter Chubb
2012-04-05 17:23 ` Peter Maydell
2012-04-03 1:55 ` [Qemu-devel] [patch V5 4/5] FreeSCALE i.MX31 support: AVIC Peter Chubb
2012-04-03 1:55 ` [Qemu-devel] [patch V5 5/5] FreeSCALE i.MX31 support: KZM-ARM11-01 evaluation board Peter Chubb
2012-04-05 17:11 ` Peter Maydell
2012-04-03 9:45 ` Andreas Färber [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=4F7AC6B0.3060002@suse.de \
--to=afaerber@suse.de \
--cc=paul@codesourcery.com \
--cc=pbonzini@redhat.com \
--cc=peter.chubb@nicta.com.au \
--cc=peter.maydell@linaro.org \
--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).