From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Chris Ball <cjb@laptop.org>, Olof Johansson <olof@lixom.net>,
Arnd Bergmann <arnd@arndb.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: linux-next: manual merge of the arm-soc tree with the mmc tree
Date: Fri, 13 Apr 2012 14:46:59 +0200 [thread overview]
Message-ID: <4F882043.1090006@atmel.com> (raw)
In-Reply-To: <87pqbdr1md.fsf@laptop.org>
On 04/12/2012 06:54 AM, Chris Ball :
> Hi,
>
> On Thu, Apr 12 2012, Stephen Rothwell wrote:
>> Today's linux-next merge of the arm-soc tree got a conflict in
>> drivers/mmc/host/Kconfig between commit a334b9550294 ("mmc: remove imxmmc
>> driver") from the mmc tree and commits a21a92c0c787 ("mmc: Kconfig: remove
>> choice between at91_mci and atmel-mci") and 62080f06de6b ("mmc:
>> atmel-mci: remove the need for CONFIG_MMC_ATMELMCI_DMA") from the arm-soc
>> tree.
>>
>> I fixed it up (see below) and can carry the fix as necessary.
>
> Thanks, Stephen.
>
> Nicolas and Arnd, these MMC Kconfig patches weren't sent to me or
> linux-mmc@ for review, so I haven't seen them before. They look
> fine, but I'd like to be in the loop directly to avoid surprises.
Yes Chris, my fault here, it is true that I should have send those
patches to you and linux-mmc.
> Do these MMC patches have any dependency on other work? It doesn't
> look like it. If that's so, I'd rather carry them in the MMC tree
> to save Stephen and Linus from dealing with the merge conflict.
Indeed, and in the meantime, it seems that these Kconfig modifications
are not as harmless as the others in the series.
I propose to redo a pull request without those two patches. We will
resend them directly through the MMC subsystem together with other
mmc-related fixes. Moreover, all this will probably make more sense as
3.5 modifications...
Best regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2012-04-13 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 4:02 linux-next: manual merge of the arm-soc tree with the mmc tree Stephen Rothwell
2012-04-12 4:54 ` Chris Ball
2012-04-13 12:46 ` Nicolas Ferre [this message]
2012-09-17 8:01 Stephen Rothwell
2012-09-24 9:36 Stephen Rothwell
2012-11-26 10:38 Stephen Rothwell
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=4F882043.1090006@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=s.hauer@pengutronix.de \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).