From: Andrew Morton <akpm@linux-foundation.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Olof Johansson <olof@lixom.net>, Colin Cross <ccross@android.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 3/3] SDHCI: 8-bit data transfer width support
Date: Tue, 29 Jun 2010 11:37:56 -0700 [thread overview]
Message-ID: <20100629113756.e8184ba2.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTim4yfMX60NoHODkc695R7k0ZwRKPVTXB_JOg7C_@mail.gmail.com>
On Mon, 28 Jun 2010 12:48:29 -0700
Grant Likely <grant.likely@secretlab.ca> wrote:
> On Mon, Jun 28, 2010 at 12:33 PM, Olof Johansson <olof@lixom.net> wrote:
> > On Mon, Jun 28, 2010 at 11:56:26AM -0700, Colin Cross wrote:
> >> These patches are not coming from the tegra/for-next branch, they are
> >> coming from Grant's devicetree-next branch. __Grant, why are these
> >> patches in your tree, and why is tegra/for-next in your tree? __It's
> >> going to cause conflicts when we rebase our for-next branch. __Please
> >> remove tegra and this sdhci patch from your tree.
> >
> > Yeah, this seems to be a mixup by Grant. I gave him a few patches I had
> > picked up locally to work with, and he seems to have published the
> > work accidentally.
>
> Hi Colin,
>
> I've fixed it now. Profuse apologies, sorry for the noise, and I owe
> you a beer or 3.
Thanks, guys - I resurrected
sdhci-8-bit-data-transfer-width-support.patch and
sdhci-dont-assign-mmc-caps-at-sdhci-directly.patch
prev parent reply other threads:[~2010-06-29 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 5:45 [PATCH 3/3] SDHCI: 8-bit data transfer width support Kyungmin Park
2010-06-28 18:39 ` Andrew Morton
2010-06-28 18:56 ` Colin Cross
2010-06-28 19:33 ` Olof Johansson
2010-06-28 19:48 ` Grant Likely
2010-06-29 18:37 ` Andrew Morton [this message]
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=20100629113756.e8184ba2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ccross@android.com \
--cc=grant.likely@secretlab.ca \
--cc=kyungmin.park@samsung.com \
--cc=linux-mmc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.