From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: "Prchal Jiří" <jiri.prchal@aksignal.cz>
Cc: nicolas.ferre@atmel.com, linux-kernel@vger.kernel.org,
Ryan Mallon <ryan@bluewatersys.com>,
plagnioj@jcrosoft.co, linux@maxim.org.za,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARCH arm: adding new board: CDU
Date: Mon, 4 Apr 2011 10:24:34 +0100 [thread overview]
Message-ID: <20110404092434.GB19841@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20110404091635.GA19841@n2100.arm.linux.org.uk>
On Mon, Apr 04, 2011 at 10:16:35AM +0100, Russell King - ARM Linux wrote:
> On Mon, Apr 04, 2011 at 11:10:42AM +0200, Prchal Jiří wrote:
> > Hi,
> > this is separated PATCH adding new board CDU.
>
> What does this have to do with
>
> "[PATCH 1/2] mmc, ARM: Rename SuperH Mobile ARM zboot helpers" ?
>
> which is the message which you hit your mailer's "reply" button on?
> Please don't pollute email threads.
Sorry, it's not as trivial as I thought. For some reason your mailer is
introducing additional message IDs in the 'References' header which are
causing the message to be incorrectly threaded. Here are the original
two messages:
From: Simon Horman <horms@verge.net.au>
Subject: [PATCH 0/2] mmc: zboot helpers
Message-Id: <1300949648-15078-1-git-send-email-horms@verge.net.au>
From: Simon Horman <horms@verge.net.au>
Subject: [PATCH 1/2] mmc, ARM: Rename SuperH Mobile ARM zboot helpers
Message-Id: <1300949648-15078-2-git-send-email-horms@verge.net.au>
And your messages:
From: Prchal Ji■í <jiri.prchal@aksignal.cz>
Subject: [PATCH] mmc, AT91: fix init fequency problem
References: <1300949648-15078-1-git-send-email-horms@verge.net.au>
<1300949648-15078-2-git-send-email-horms@verge.net.au>
In-Reply-To: <1300949648-15078-2-git-send-email-horms@verge.net.au>
From: Prchal Ji■í <jiri.prchal@aksignal.cz>
Subject: [PATCH] ARCH arm: adding new board: CDU
References: <1300949648-15078-1-git-send-email-horms@verge.net.au>
<1300949648-15078-2-git-send-email-horms@verge.net.au>
<4D8B2068.60402@aksignal.cz> <4D8BA47B.8050904@bluewatersys.com>
In-Reply-To: <4D8BA47B.8050904@bluewatersys.com>
both of which reference Simon's unrelated emails. No idea how you're
doing that, but both of your messages seem to be completely unrelated
to Simon's two.
next prev parent reply other threads:[~2011-04-04 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1300949648-15078-1-git-send-email-horms@verge.net.au>
[not found] ` <1300949648-15078-2-git-send-email-horms@verge.net.au>
2011-03-24 9:10 ` [PATCH] mmc, AT91: fix init fequency problem Prchal Jiří
2011-03-24 10:20 ` [PATCH 1/2] ALSA: ASoc: TLV320AIC3X: ad SPI and clock on GPIO2 or BCLK Prchal Jiří
2011-04-02 8:26 ` [alsa-devel] " Mark Brown
2011-04-04 7:49 ` Prchal Jiří
2011-04-04 8:03 ` Mark Brown
2011-04-04 8:01 ` [PATCH] ALSA: ASoc: new functions snd_soc_7_8_* Prchal Jiří
2011-04-04 8:05 ` Mark Brown
2011-03-24 10:43 ` [PATCH 2/2] ALSA: ASoc: putting together AT91SAM9260 and TLV320AIC3X Prchal Jiří
2011-03-24 20:07 ` Ryan Mallon
2011-04-04 8:57 ` Prchal Jiří
2011-04-04 20:07 ` Ryan Mallon
2011-04-04 9:10 ` [PATCH] ARCH arm: adding new board: CDU Prchal Jiří
2011-04-04 9:16 ` Russell King - ARM Linux
2011-04-04 9:24 ` Russell King - ARM Linux [this message]
2011-04-04 20:25 ` Ryan Mallon
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=20110404092434.GB19841@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=jiri.prchal@aksignal.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.co \
--cc=ryan@bluewatersys.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
all inboxes | Powered by JetHome®