From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greentime Hu <green.hu@gmail•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Masahiro Yamada <masahiroy@kernel•org>,
Randy Dunlap <rdunlap@infradead•org>,
"Steven Rostedt (VMware)" <rostedt@goodmis•org>
Subject: linux-next: manual merge of the nds32 tree with Linus' tree
Date: Thu, 9 Sep 2021 09:52:24 +1000 [thread overview]
Message-ID: <20210909095224.43f23be0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
Hi all,
Today's linux-next merge of the nds32 tree got a conflict in:
arch/nds32/Kconfig
between commit:
4aae683f1327 ("tracing: Refactor TRACE_IRQFLAGS_SUPPORT in Kconfig")
from Linus' tree and commit:
36b9b1975393 ("nds32: add a Kconfig symbol for LOCKDEP_SUPPORT")
from the nds32 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.
--
Cheers,
Stephen Rothwell
diff --cc arch/nds32/Kconfig
index aea26e739543,a20b42d4bdb6..000000000000
--- a/arch/nds32/Kconfig
+++ b/arch/nds32/Kconfig
@@@ -63,6 -63,12 +62,9 @@@ config GENERIC_LOCKBREA
def_bool y
depends on PREEMPTION
+ config LOCKDEP_SUPPORT
+ def_bool y
+
-config TRACE_IRQFLAGS_SUPPORT
- def_bool y
-
config STACKTRACE_SUPPORT
def_bool y
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2021-09-08 23:52 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=20210909095224.43f23be0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=green.hu@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=masahiroy@kernel$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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