From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Nicolin Chen <Guangyu.Chen@freescale.com>,
shawn.guo@linaro.org, kernel@pengutronix.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, rob.herring@calxeda.com,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, rob@landley.net,
mturquette@linaro.org
Subject: Re: [PATCH] ARM: imx6q: Add missing esai_ahb clock to current clock tree
Date: Thu, 9 Jan 2014 15:01:41 +0000 [thread overview]
Message-ID: <20140109150141.GD27432@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140109075525.GO6750@pengutronix.de>
Sascha, your messages have the Mail-Followup-To: header...
Mail-Followup-To: Nicolin Chen <Guangyu.Chen@freescale.com>,
shawn.guo@linaro.org, kernel@pengutronix.de, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
rob.herring@calxeda.com, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, rob@landley.net, mturquette@linaro.org
resulting in me (and others) getting mails marked as To: me where they're
not supposed to be To: me in the first place.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-09 15:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 3:04 [PATCH] ARM: imx6q: Add missing esai_ahb clock to current clock tree Nicolin Chen
2014-01-09 3:58 ` Shawn Guo
2014-01-09 3:49 ` Nicolin Chen
2014-01-09 6:57 ` Shawn Guo
2014-01-09 7:41 ` Nicolin Chen
2014-01-09 7:58 ` Sascha Hauer
2014-01-09 7:51 ` Nicolin Chen
2014-01-09 7:55 ` Sascha Hauer
2014-01-09 14:57 ` Gerhard Sittig
2014-01-09 15:01 ` Russell King - ARM Linux [this message]
2014-01-10 10:06 ` Sascha Hauer
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=20140109150141.GD27432@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Guangyu.Chen@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@linaro.org \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.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