[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <B4102448-9875-4C8A-94A1-E2EDFC5011E2@codeaurora.org>
Date: Wed, 26 Feb 2014 13:15:06 -0600
From: Kumar Gala <galak@...eaurora.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
linux-arm-kernel@...ts.infradead.org, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: linux-next: manual merge of the crypto tree with the arm-soc tree
On Feb 25, 2014, at 10:01 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Herbert,
>
> Today's linux-next merge of the crypto tree got a conflict in
> drivers/char/hw_random/Kconfig between commit 2257ffbca73c ("hwrng: msm:
> switch Kconfig to ARCH_QCOM depends") from the arm-soc tree and commit
> f9bee046c915 ("hwrng: msm: switch Kconfig to ARCH_QCOM depends") from the
> crypto tree.
>
> Two version of the same patch ... I just kept the arm-soc version.
Herbert,
Was trying to keep all the ARCH_QCOM Kconfig updates together and via arm-soc.git
thanks
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
--
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