[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAQ0ZWQU+jiUYpHKWh=qh6O4qbtj7kpHiw1LRyE58vdPXfq2vA@mail.gmail.com>
Date: Wed, 12 Aug 2015 13:40:56 +0800
From: Shawn Guo <shawn.guo@...aro.org>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Victoria Milhoan <vicki.milhoan@...escale.com>,
Shengjiu Wang <shengjiu.wang@...escale.com>
Subject: Re: linux-next: manual merge of the crypto tree with the imx-mxs tree
Herbert,
On Wed, Aug 12, 2015 at 1:18 PM, Herbert Xu <herbert@...dor.apana.org.au> wrote:
> On Wed, Aug 12, 2015 at 01:22:39PM +1000, Stephen Rothwell wrote:
>>
>> Today's linux-next merge of the crypto tree got a conflict in:
>>
>> arch/arm/configs/imx_v6_v7_defconfig
>>
>> between commit:
>>
>> 351265f46291 ("ARM: imx_v6_v7_defconfig: build in audio driver")
>>
>> from the imx-mxs tree and commit:
>>
>> ab86ca0755ec ("ARM: imx_v6_v7_defconfig: Select CAAM")
>>
>> from the crypto tree.
>>
>> I fixed it up (they both removed the same line) and can carry the fix
>> as necessary (no action is required).
Please leave i.MX architecture patches (i.MX patches under arch/arm/)
to me to handle in the future, so that we can avoid such unnecessary
merge conflict.
Shawn
--
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