From: Arnd Bergmann <arnd@arndb.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Stephen Warren <swarren@nvidia.com>,
nicolas.pitre@linaro.org, Shawn Guo <shawn.guo@linaro.org>,
devicetree-discuss@lists.ozlabs.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
Olof Johansson <olof@lixom.net>, Chris Ball <cjb@laptop.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH REPOST 1/2] arm/dt: Tegra: Update SDHCI nodes to match bindings
Date: Tue, 20 Sep 2011 23:01:56 +0200 [thread overview]
Message-ID: <201109202301.56983.arnd@arndb.de> (raw)
In-Reply-To: <201109202134.50242.arnd@arndb.de>
On Tuesday 20 September 2011, Arnd Bergmann wrote:
> On Tuesday 20 September 2011, Grant Likely wrote:
> > On Tue, Sep 20, 2011 at 07:43:29PM +0200, Arnd Bergmann wrote:
> > > On Tuesday 20 September 2011, Stephen Warren wrote:
> > > > The bindings were recently updated to have separate properties for each
> > > > type of GPIO. Update the Device Tree source to match that.
> > > >
> > > > Signed-off-by: Stephen Warren <swarren@nvidia.com>
> > > > Acked-by: Olof Johansson <olof@lixom.net>
> > > > ---
> > > > I'd previously sent these to Grant assuming they'd go in his dt/next branch,
> > > > but perhaps these should go in through Arnd's arm-soc next/dt branch?
> > > >
> > >
> > > Which tree has the update that changed the bindings? I think it should
> > > go into the same one.
> > >
> > > If it's already upstream, I can take it into the fixes branch.
> >
> > Already upstream
>
> Ok, I see. I've applied both patches to the fixes branch and will send
> it out with the next pull request for 3.1 to Linus then.
Sorry, I just noticed that the second patch is not a bug fix, so I took it out
again and kept only patch 1/2 in the fixes branch for 3.1.
Should I take the other one as well? It's probably better to let that
go the proper way through the tegra tree for 3.2, right?
Arnd
next prev parent reply other threads:[~2011-09-20 21:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 16:46 [PATCH REPOST 1/2] arm/dt: Tegra: Update SDHCI nodes to match bindings Stephen Warren
2011-09-20 16:46 ` [PATCH REPOST 2/2] arm/dt: Tegra: Add support-8bit to SDHCI nodes Stephen Warren
[not found] ` <1316537186-26753-2-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-09-20 17:41 ` Grant Likely
[not found] ` <1316537186-26753-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2011-09-20 17:42 ` [PATCH REPOST 1/2] arm/dt: Tegra: Update SDHCI nodes to match bindings Grant Likely
2011-09-20 17:43 ` Arnd Bergmann
2011-09-20 17:59 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF04B732161E-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-09-20 18:07 ` Chris Ball
2011-09-20 18:07 ` Grant Likely
[not found] ` <20110920180731.GL7781-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-09-20 19:34 ` Arnd Bergmann
2011-09-20 21:01 ` Arnd Bergmann [this message]
2011-09-20 21:39 ` Olof Johansson
2011-09-22 14:40 ` Arnd Bergmann
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=201109202301.56983.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=olof@lixom.net \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.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