From: Mark Brown <broonie@kernel.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
linaro-kernel@lists.linaro.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 1/3] ARM: dts: Leave Exynos5250 SPI controller disabled by default
Date: Tue, 10 Dec 2013 11:13:09 +0000 [thread overview]
Message-ID: <20131210111309.GD29268@sirena.org.uk> (raw)
In-Reply-To: <CAD=FV=XEKUFWEM-30Bx0pVBOT8X0zXsdHyzq=pDY8TOcdGHgRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
On Mon, Dec 09, 2013 at 04:57:01PM -0800, Doug Anderson wrote:
> I'm a little surprised that I don't see removal of spi_0 on SMDK5250.
> When I apply your patch to ToT Linux I still see this in
> "exynos5250-smdk5250.dts":
> spi_0: spi@12d20000 {
> status = "disabled";
> };
I suspect that one went AWOL during rebasing - these have been kicking
around since September. Resent with that added.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-10 11:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 12:15 [PATCH 1/3] ARM: dts: Leave Exynos5250 SPI controller disabled by default Mark Brown
2013-11-25 12:15 ` [PATCH 2/3] ARM: dts: Disable I2C controllers by default on Exynos5250 Mark Brown
2013-11-25 12:15 ` [PATCH 3/3] ARM: dts: Rename Exynos5250 ChromeOS common file to have exynos prefix Mark Brown
2013-12-20 23:09 ` Kukjin Kim
2013-12-20 23:37 ` Kukjin Kim
2013-12-21 0:57 ` Doug Anderson
2013-12-21 1:11 ` Kukjin Kim
2013-12-09 15:23 ` [PATCH 1/3] ARM: dts: Leave Exynos5250 SPI controller disabled by default Tomasz Figa
2013-12-09 21:07 ` Kukjin Kim
2013-12-10 0:48 ` Doug Anderson
2013-12-10 0:57 ` Doug Anderson
2013-12-10 11:13 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-10 11:07 Mark Brown
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=20131210111309.GD29268@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/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