From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: "Andreas Färber" <afaerber@suse.de>, linux-samsung-soc@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Vincent Palatin <vpalatin@chromium.org>,
Doug Anderson <dianders@chromium.org>,
Tomasz Figa <t.figa@samsung.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Kukjin Kim <kgene@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: Update exynos5250-spring with mmc node changes
Date: Thu, 19 Feb 2015 12:46:54 +0100 [thread overview]
Message-ID: <54E5CD2E.9070608@collabora.co.uk> (raw)
In-Reply-To: <1424275812-6797-1-git-send-email-afaerber@suse.de>
Hello Andreas,
On 02/18/2015 05:10 PM, Andreas Färber wrote:
> Resolve a merge conflict with mmc refactoring aaa25a5a33cb ("ARM: dts:
> unuse the slot-node and deprecate the supports-highspeed for dw-mmc in
> exynos") by dropping the slot@0 nodes, moving its bus-width property to
> the mmc node and replacing supports-highspeed with cap-{mmc,sd}-highspeed,
> matching exynos5250-snow.
>
> Cc: Jaehoon Chung <jh80.chung@samsung.com>
> Fixes: 53dd4138bb0a ("ARM: dts: Add exynos5250-spring device tree")
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
> arch/arm/boot/dts/exynos5250-spring.dts | 16 ++++------------
> 1 file changed, 4 insertions(+), 12 deletions(-)
>
Reviewed-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Best regards,
Javier
next prev parent reply other threads:[~2015-02-19 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 16:10 [PATCH] ARM: dts: Update exynos5250-spring with mmc node changes Andreas Färber
2015-02-19 11:46 ` Javier Martinez Canillas [this message]
2015-03-16 14:55 ` Andreas Färber
2015-03-17 16:27 ` Kukjin Kim
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=54E5CD2E.9070608@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jh80.chung@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=t.figa@samsung.com \
--cc=vpalatin@chromium.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