From: Mark Brown <broonie@kernel.org>
To: Kevin Hilman <khilman@baylibre.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzk@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
soc@lists.linux.dev, Thomas Huth <thuth@redhat.com>
Subject: linux-next: manual merge of the omap tree with the arm-soc tree
Date: Fri, 2 Oct 2026 12:57:59 +0100 [thread overview]
Message-ID: <ar-cR1FLtZBS7dpn@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Hi all,
FIXME: Add author(s)/SOB of conflicting commits.
Today's linux-next merge of the omap tree got a conflict in:
arch/arm/mach-omap2/control.h
between commit:
cbd33c61480b8 ("ARM: omap2: remove omap24xx support")
from the arm-soc tree and commit:
9d458ad3ec155 ("ARM: OMAP2+: Replace __ASSEMBLY__ with __ASSEMBLER__")
from the omap 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.
diff --cc arch/arm/mach-omap2/control.h
index 3ab1c6e6dde67,e4f4b16958084..0000000000000
--- a/arch/arm/mach-omap2/control.h
+++ b/arch/arm/mach-omap2/control.h
@@@ -18,7 -18,11 +18,7 @@@
#include "am33xx.h"
- #ifndef __ASSEMBLY__
+ #ifndef __ASSEMBLER__
-#define OMAP242X_CTRL_REGADDR(reg) \
- OMAP2_L4_IO_ADDRESS(OMAP242X_CTRL_BASE + (reg))
-#define OMAP243X_CTRL_REGADDR(reg) \
- OMAP2_L4_IO_ADDRESS(OMAP243X_CTRL_BASE + (reg))
#define OMAP343X_CTRL_REGADDR(reg) \
OMAP2_L4_IO_ADDRESS(OMAP343X_CTRL_BASE + (reg))
#define AM33XX_CTRL_REGADDR(reg) \
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-10-02 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 11:57 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-09 22:50 Stephen Rothwell
2023-01-19 10:11 ` Tony Lindgren
2015-01-20 0:09 Stephen Rothwell
2015-01-20 17:10 ` Tony Lindgren
2015-01-20 18:24 ` Olof Johansson
2015-01-20 18:40 ` Tony Lindgren
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=ar-cR1FLtZBS7dpn@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=soc@lists.linux.dev \
--cc=thuth@redhat.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
all inboxes | Powered by JetHome®