archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <>
To: Herbert Xu <>,
	Olof Johansson <>, Arnd Bergmann <>,
	ARM <>
Cc: Linux-Next Mailing List <>,
	Linux Kernel Mailing List <>,
	Amelie Delaunay <>,
	Alexandre TORGUE <>,
	Fabien DESSENNE <>
Subject: linux-next: manual merge of the crypto tree with the arm-soc tree
Date: Thu, 20 Apr 2017 11:23:35 +1000	[thread overview]
Message-ID: <> (raw)

Hi all,

Today's linux-next merge of the crypto tree got a conflict in:


between commit:

  4cc627472cd6 ("ARM: dts: stm32: enable RTC on stm32746g-eval")

from the arm-soc tree and commit:

  2e3db2931875 ("ARM: dts: stm32: enable CRC on stm32746g-eval board")

from the crypto 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.

Stephen Rothwell

diff --cc arch/arm/boot/dts/stm32746g-eval.dts
index b5207588bdcb,0dc18a0f0940..000000000000
--- a/arch/arm/boot/dts/stm32746g-eval.dts
+++ b/arch/arm/boot/dts/stm32746g-eval.dts
@@@ -89,10 -89,10 +89,14 @@@
  	clock-frequency = <25000000>;
+ &crc {
+ 	status = "okay";
+ };
 +&rtc {
 +	status = "okay";
  &usart1 {
  	pinctrl-0 = <&usart1_pins_a>;
  	pinctrl-names = "default";

             reply	other threads:[~2017-04-20  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20  1:23 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-15 20:55 Mark Brown
2014-02-26  4:01 Stephen Rothwell
2014-02-26 19:15 ` Kumar Gala
2014-02-26 21:58   ` Herbert Xu

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: linux-next: manual merge of the crypto tree with the arm-soc tree' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).