From: Thierry Reding <thierry.reding@kernel.org>
To: Alexandre Torgue <alexandre.torgue@st.com>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Raphael Gallais-Pou <raphael.gallais-pou@foss.st.com>
Subject: linux-next: manual merge of stm32 tree with the arm-soc tree
Date: Fri, 08 May 2026 11:55:06 +0200 [thread overview]
Message-ID: <b44aea932425f52a9d0921c127c1f839@kernel.org> (raw)
Hi all,
Today's linux-next merge of the stm32 tree got a conflict in:
arch/arm64/configs/defconfig
between commit:
f54f7979ff88 ("arm64: defconfig: Move entries to match savedefconfig")
from the arm-soc tree and commit:
515aa8b11884 ("arm64: defconfig: Enable STMicroelectronics STM32 display support")
from the stm32 tree.
This one is weird. It looks like a version of the stm32 tree was
already merged into Linus' tree as:
407b861f4d0c ("arm64: defconfig: Enable STMicroelectronics STM32 display support")
And then reset to the slightly older version above. Please make sure to
have your stm32-next branch point to the version that ended up getting
merged into Linus' tree, or roll it forward to v7.1-rc1 so we don't end
up trying to pull (nearly) the same version of the code again.
I fixed it up by using the version from arm-soc. 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.
reply other threads:[~2026-05-08 9:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b44aea932425f52a9d0921c127c1f839@kernel.org \
--to=thierry.reding@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=alexandre.torgue@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox