From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kees Cook <keescook@chromium•org>,
Thomas Bogendoerfer <tsbogend@alpha•franken.de>
Cc: Alexander Lobakin <alobakin@pm•me>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Sami Tolvanen <samitolvanen@google•com>
Subject: Re: linux-next: manual merge of the kspp tree with the mips tree
Date: Tue, 23 Feb 2021 10:49:50 +1100 [thread overview]
Message-ID: <20210223104950.1f754320@canb.auug.org.au> (raw)
In-Reply-To: <20210215074726.60c45281@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
Hi all,
On Mon, 15 Feb 2021 07:47:26 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> On Mon, 18 Jan 2021 15:08:04 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > Today's linux-next merge of the kspp tree got a conflict in:
> >
> > include/asm-generic/vmlinux.lds.h
> >
> > between commits:
> >
> > 9a427556fb8e ("vmlinux.lds.hf41b233de0ae: catch compound literals into data and BSS")
> > f41b233de0ae ("vmlinux.lds.h: catch UBSAN's "unnamed data" into data")
> >
> > from the mips tree and commit:
> >
> > dc5723b02e52 ("kbuild: add support for Clang LTO")
> >
> > from the kspp tree.
> >
> > I fixed it up (9a427556fb8e and dc5723b02e52 made the same change to
> > DATA_MAIN, which conflicted with the change in f41b233de0ae) 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.
>
> With the merge window about to open, this is a reminder that this
> conflict still exists.
This is now a conflict between the kspp tree and Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-02-22 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 4:08 linux-next: manual merge of the kspp tree with the mips tree Stephen Rothwell
2021-02-14 20:47 ` Stephen Rothwell
2021-02-22 23:49 ` Stephen Rothwell [this message]
2021-02-23 10:44 ` Alexander Lobakin
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=20210223104950.1f754320@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alobakin@pm$(echo .)me \
--cc=keescook@chromium$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=samitolvanen@google$(echo .)com \
--cc=tsbogend@alpha$(echo .)franken.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