From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul@pwsan.com>
Cc: Leonardo Bras <leobras@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Palmer Dabbelt <palmer@rivosinc.com>,
Yujie Liu <yujie.liu@intel.com>
Subject: linux-next: manual merge of the rcu tree with the risc-v tree
Date: Mon, 15 Apr 2024 12:32:47 +1000 [thread overview]
Message-ID: <20240415123247.0d27eb39@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
Hi all,
Today's linux-next merge of the rcu tree got a conflict in:
arch/riscv/include/asm/cmpxchg.h
between commits:
07a0a41cb77d ("riscv/cmpxchg: Deduplicate cmpxchg() asm and macros")
54280ca64626 ("riscv/cmpxchg: Implement cmpxchg for variables of size 1 and 2")
from the risc-v tree and commit:
b5e49f1af563 ("riscv: Emulate one-byte cmpxchg")
from the rcu tree.
I fixed it up (I just used the former as the latter seems to no longer be
needed - I also undid the change to arch/riscv/Kconfig from the latter)
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-04-15 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 2:32 Stephen Rothwell [this message]
2024-04-15 4:44 ` linux-next: manual merge of the rcu tree with the risc-v tree Paul E. McKenney
2024-04-15 18:20 ` Palmer Dabbelt
2024-04-15 21:20 ` Paul E. McKenney
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=20240415123247.0d27eb39@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul@pwsan.com \
--cc=paulmck@kernel.org \
--cc=yujie.liu@intel.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