From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <keescook@google.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Emese Revfy <re.emese@gmail.com>
Subject: linux-next: manual merge of the kspp tree with Linus' tree
Date: Tue, 8 Nov 2016 13:31:30 +1100 [thread overview]
Message-ID: <20161108133130.24c065f8@canb.auug.org.au> (raw)
Hi Kees,
FIXME: Add owner of second tree to To:
Add author(s)/SOB of conflicting commits.
Today's linux-next merge of the kspp tree got a conflict in:
mm/page_alloc.c
scripts/gcc-plugins/latent_entropy_plugin.c
between commits:
38addce8b600 ("gcc-plugins: Add latent_entropy plugin")
0766f788eb72 ("latent_entropy: Mark functions with __latent_entropy")
58bea4144d23 ("latent_entropy: Fix wrong gcc code generation with 64 bit variables")
from Linus' tree and commits:
2a5448668a3c ("gcc-plugins: Add latent_entropy plugin")
09dd109d8241 ("latent_entropy: Mark functions with __latent_entropy")
from the kspp tree.
I fixed it up (I used the version from Linus' tree) 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.
Kees, maybe you could clean up the kspp tree.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-11-08 2:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 2:31 Stephen Rothwell [this message]
2016-11-08 18:44 ` linux-next: manual merge of the kspp tree with Linus' tree Kees Cook
2017-02-08 1:41 Stephen Rothwell
2020-01-06 4:48 Stephen Rothwell
2020-04-08 2:00 Stephen Rothwell
2020-06-29 5:43 Stephen Rothwell
2020-10-09 6:41 Stephen Rothwell
2021-06-11 6:17 Stephen Rothwell
2021-09-14 4:04 Stephen Rothwell
2022-03-15 10:49 Stephen Rothwell
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=20161108133130.24c065f8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=re.emese@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;
as well as URLs for NNTP newsgroup(s).