Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Andreas Larsson <andreas@gaisler.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Rosen Penev <rosenp@gmail.com>
Subject: linux-next: manual merge of the sparc tree with the mm-nonmm-unstable tree
Date: Mon, 15 Jun 2026 14:00:13 +0100	[thread overview]
Message-ID: <ai_3Xf5aR0936CyG@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

Hi all,

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

  arch/sparc/include/asm/asm-prototypes.h

between commit:

  4fc4802c9d563 ("sparc: add _mcount() prototype")

from the mm-nonmm-unstable tree and commits:

  1919c0e50000e ("sparc: add _mcount() prototype")
  2416b30ec23fd ("sparc: Export mcount for Clang-built modules")

from the sparc 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 --combined arch/sparc/include/asm/asm-prototypes.h
index 270c51017212a,a39a24c53216b..0000000000000
--- a/arch/sparc/include/asm/asm-prototypes.h
+++ b/arch/sparc/include/asm/asm-prototypes.h
@@@ -26,6 -26,7 +26,7 @@@ void *memset(void *s, int c, size_t n)
  typedef int TItype __attribute__((mode(TI)));
  TItype __multi3(TItype a, TItype b);
  void _mcount(void);
+ void mcount(void);
  
  s64 __ashldi3(s64, int);
  s64 __lshrdi3(s64, int);

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2026-06-15 13:00 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=ai_3Xf5aR0936CyG@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andreas@gaisler.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rosenp@gmail.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