From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Cooper <jason@lakedaemon.net>, <andrew@lunn.ch>,
<gregory.clement@free-electrons.com>,
<linux-arm-kernel@lists.infradead.org>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Romain Perier <romain.perier@free-electrons.com>,
Lee Jones <lee.jones@linaro.org>,
Maxime Coquelin <maxime.coquelin@st.com>
Subject: linux-next: manual merge of the mvebu tree with the arm-soc tree
Date: Thu, 14 Apr 2016 09:29:20 +1000 [thread overview]
Message-ID: <20160414092920.41fb4ebe@canb.auug.org.au> (raw)
Hi all,
Today's linux-next merge of the mvebu tree got a conflict in:
arch/arm/configs/multi_v7_defconfig
between commit:
6d54fb8a08a7 ("ARM: multi_v7_defconfig: Enable ST's HW Random Number Generator")
from the arm-soc tree and commit:
fe767240934f ("ARM: configs: Enabling the new Marvell's cryptographic engine driver for multi_v7_defconfig")
from the mvebu tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc arch/arm/configs/multi_v7_defconfig
index 811b41823baa,392e970b60c7..000000000000
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@@ -837,8 -829,7 +837,9 @@@ CONFIG_LOCKUP_DETECTOR=
CONFIG_CRYPTO_DEV_TEGRA_AES=y
CONFIG_CPUFREQ_DT=y
CONFIG_KEYSTONE_IRQ=y
+CONFIG_HW_RANDOM=y
+CONFIG_HW_RANDOM_ST=y
+ CONFIG_CRYPTO_DEV_MARVELL_CESA=m
CONFIG_CRYPTO_DEV_SUN4I_SS=m
CONFIG_CRYPTO_DEV_ROCKCHIP=m
CONFIG_ARM_CRYPTO=y
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Cooper <jason@lakedaemon.net>,
andrew@lunn.ch, gregory.clement@free-electrons.com,
linux-arm-kernel@lists.infradead.org,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Romain Perier <romain.perier@free-electrons.com>,
Lee Jones <lee.jones@linaro.org>,
Maxime Coquelin <maxime.coquelin@st.com>
Subject: linux-next: manual merge of the mvebu tree with the arm-soc tree
Date: Thu, 14 Apr 2016 09:29:20 +1000 [thread overview]
Message-ID: <20160414092920.41fb4ebe@canb.auug.org.au> (raw)
Hi all,
Today's linux-next merge of the mvebu tree got a conflict in:
arch/arm/configs/multi_v7_defconfig
between commit:
6d54fb8a08a7 ("ARM: multi_v7_defconfig: Enable ST's HW Random Number Generator")
from the arm-soc tree and commit:
fe767240934f ("ARM: configs: Enabling the new Marvell's cryptographic engine driver for multi_v7_defconfig")
from the mvebu tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc arch/arm/configs/multi_v7_defconfig
index 811b41823baa,392e970b60c7..000000000000
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@@ -837,8 -829,7 +837,9 @@@ CONFIG_LOCKUP_DETECTOR=
CONFIG_CRYPTO_DEV_TEGRA_AES=y
CONFIG_CPUFREQ_DT=y
CONFIG_KEYSTONE_IRQ=y
+CONFIG_HW_RANDOM=y
+CONFIG_HW_RANDOM_ST=y
+ CONFIG_CRYPTO_DEV_MARVELL_CESA=m
CONFIG_CRYPTO_DEV_SUN4I_SS=m
CONFIG_CRYPTO_DEV_ROCKCHIP=m
CONFIG_ARM_CRYPTO=y
WARNING: multiple messages have this Message-ID (diff)
From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the mvebu tree with the arm-soc tree
Date: Thu, 14 Apr 2016 09:29:20 +1000 [thread overview]
Message-ID: <20160414092920.41fb4ebe@canb.auug.org.au> (raw)
Hi all,
Today's linux-next merge of the mvebu tree got a conflict in:
arch/arm/configs/multi_v7_defconfig
between commit:
6d54fb8a08a7 ("ARM: multi_v7_defconfig: Enable ST's HW Random Number Generator")
from the arm-soc tree and commit:
fe767240934f ("ARM: configs: Enabling the new Marvell's cryptographic engine driver for multi_v7_defconfig")
from the mvebu tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc arch/arm/configs/multi_v7_defconfig
index 811b41823baa,392e970b60c7..000000000000
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@@ -837,8 -829,7 +837,9 @@@ CONFIG_LOCKUP_DETECTOR=
CONFIG_CRYPTO_DEV_TEGRA_AES=y
CONFIG_CPUFREQ_DT=y
CONFIG_KEYSTONE_IRQ=y
+CONFIG_HW_RANDOM=y
+CONFIG_HW_RANDOM_ST=y
+ CONFIG_CRYPTO_DEV_MARVELL_CESA=m
CONFIG_CRYPTO_DEV_SUN4I_SS=m
CONFIG_CRYPTO_DEV_ROCKCHIP=m
CONFIG_ARM_CRYPTO=y
next reply other threads:[~2016-04-13 23:29 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 23:29 Stephen Rothwell [this message]
2016-04-13 23:29 ` linux-next: manual merge of the mvebu tree with the arm-soc tree Stephen Rothwell
2016-04-13 23:29 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-05-09 23:41 Stephen Rothwell
2022-05-09 23:41 ` Stephen Rothwell
2022-05-10 13:59 ` Krzysztof Kozlowski
2022-05-10 13:59 ` Krzysztof Kozlowski
2022-05-10 14:42 ` Arnd Bergmann
2022-05-10 14:42 ` Arnd Bergmann
2018-05-16 22:47 Stephen Rothwell
2018-05-16 22:47 ` Stephen Rothwell
2017-04-11 22:34 Stephen Rothwell
2017-04-11 22:34 ` Stephen Rothwell
2017-04-12 8:23 ` Gregory CLEMENT
2017-04-12 8:23 ` Gregory CLEMENT
2017-04-12 10:51 ` Stephen Rothwell
2017-04-12 10:51 ` Stephen Rothwell
2016-02-17 23:33 Stephen Rothwell
2016-02-17 23:33 ` Stephen Rothwell
2016-02-17 23:33 ` Stephen Rothwell
2015-12-02 11:12 Mark Brown
2015-12-02 11:12 ` Mark Brown
2015-12-02 11:12 ` Mark Brown
2015-12-02 11:18 ` Mark Brown
2015-12-02 11:18 ` Mark Brown
2015-12-02 11:21 ` Arnd Bergmann
2015-12-02 11:21 ` Arnd Bergmann
2015-12-02 13:49 ` Gregory CLEMENT
2015-12-02 13:49 ` Gregory CLEMENT
2015-12-02 15:09 ` Arnd Bergmann
2015-12-02 15:09 ` Arnd Bergmann
2015-10-31 23:35 Stephen Rothwell
2015-10-31 23:35 ` Stephen Rothwell
2015-10-31 23:35 ` Stephen Rothwell
2015-01-13 0:20 Stephen Rothwell
2015-01-13 0:20 ` Stephen Rothwell
2015-01-13 0:20 ` Stephen Rothwell
2015-01-13 1:05 ` Andrew Lunn
2015-01-13 1:05 ` Andrew Lunn
2014-05-06 1:07 Stephen Rothwell
2014-05-06 1:07 ` Stephen Rothwell
2014-05-06 1:07 ` Stephen Rothwell
2014-05-06 1:13 ` Olof Johansson
2014-05-06 1:13 ` Olof Johansson
2014-05-06 1:13 ` Olof Johansson
2014-03-18 0:21 Stephen Rothwell
2014-03-18 0:21 ` Stephen Rothwell
2014-03-18 0:21 ` Stephen Rothwell
2014-02-26 1:46 Stephen Rothwell
2014-02-26 1:46 ` Stephen Rothwell
2014-02-26 1:46 ` Stephen Rothwell
2013-08-19 6:05 Stephen Rothwell
2013-08-19 6:05 ` Stephen Rothwell
2013-08-19 6:05 ` Stephen Rothwell
2013-08-19 20:57 ` Jason Cooper
2013-08-19 20:57 ` Jason Cooper
2013-08-19 21:09 ` Olof Johansson
2013-08-19 21:09 ` Olof Johansson
2013-08-19 21:09 ` Olof Johansson
2013-08-19 21:38 ` Jason Cooper
2013-08-19 21:38 ` Jason Cooper
2013-08-19 21:38 ` Jason Cooper
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=20160414092920.41fb4ebe@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=olof@lixom.net \
--cc=romain.perier@free-electrons.com \
/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.