From: broonie@kernel•org
To: Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@redhat•com>, "H . Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: David Sterba <dsterba@suse•com>,
Josh Poimboeuf <jpoimboe@kernel•org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: manual merge of the tip tree with the origin tree
Date: Thu, 27 Apr 2023 14:43:13 +0100 [thread overview]
Message-ID: <20230427134313.45596-1-broonie@kernel.org> (raw)
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
tools/objtool/check.c
between commit:
f372463124df5 ("btrfs: mark btrfs_assertfail() __noreturn")
from the origin tree and commits:
071c44e427815 ("sched/idle: Mark arch_cpu_idle_dead() __noreturn")
09c5ae30d0075 ("btrfs: Mark btrfs_assertfail() __noreturn")
9ea7e6b62c2bd ("init: Mark [arch_call_]rest_init() __noreturn")
from the tip 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 tools/objtool/check.c
index 931cdb7dba190,5b600bbf2389b..0000000000000
--- a/tools/objtool/check.c
+++ b/tools/objtool/check.c
next reply other threads:[~2023-04-27 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 13:43 broonie [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-04 13:18 linux-next: manual merge of the tip tree with the origin tree Mark Brown
2023-05-04 14:16 ` Dave Hansen
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=20230427134313.45596-1-broonie@kernel.org \
--to=broonie@kernel$(echo .)org \
--cc=dsterba@suse$(echo .)com \
--cc=hpa@zytor$(echo .)com \
--cc=jpoimboe@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/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