[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAH9JG2UUznpqWyO-obQVTvTovBe1xBXNrFjSgnu9DH6xdecToA@mail.gmail.com>
Date: Wed, 22 Feb 2012 11:32:34 +0900
From: Kyungmin Park <kyungmin.park@...sung.com>
To: Kukjin Kim <kgene.kim@...sung.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Chris Ball <cjb@...top.org>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jaehoon Chung <jh80.chung@...sung.com>,
Thomas Abraham <thomas.abraham@...aro.org>
Subject: Re: linux-next: manual merge of the mmc tree with the s5p tree
Hi,
I'm really disappointed with samsung sdhci merge. we sent several
patches, one month or two month ago. e.g., simple patch adding caps2
overrides feature.
To resolve these issue fianlly. can you move all mmc related things to
include/linux/platform_da
ta/ and controlled by mmc maintainer?
I hope no more dependency with arch codes and drivers codes.
Thank you,
Kyungmin Park
On 2/22/12, Kukjin Kim <kgene.kim@...sung.com> wrote:
> Stephen Rothwell wrote:
>>
>> Hi Chris,
>>
> Hi Stephen,
>
>> Today's linux-next merge of the mmc tree got a conflict in
>> drivers/mmc/host/sdhci-s3c.c between commit bd0955ed6b1b ("mmc:
>> sdhci-s3c: add platform data for the second capability") from the s5p
>> tree and commit 7880741a0625 ("mmc: sdhci-s3c: derive transfer width host
>> capability from max_width in platform data") from the mmc tree.
>>
>> Just context changes. I fixed it up (see below) and can carry the fix as
>> necessary.
>
> Look ok to me, and let me carry following when it is required.
>
> Thanks.
>
> Best regards,
> Kgene.
> --
> Kukjin Kim <kgene.kim@...sung.com>, Senior Engineer,
> SW Solution Development Team, Samsung Electronics Co., Ltd.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists