From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <keescook@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: linux-next: manual merge of the kspp tree with the kbuild tree
Date: Thu, 26 Aug 2021 16:48:09 +1000 [thread overview]
Message-ID: <20210826164809.402222af@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
Hi all,
Today's linux-next merge of the kspp tree got a conflict in:
Makefile
between commit:
389640bf8d17 ("Makefile: remove stale cc-option checks")
from the kbuild tree and commits:
2d931b634b81 ("Makefile: Enable -Warray-bounds")
7d8aac16a0a8 ("Makefile: Enable -Wzero-length-bounds")
from the kspp tree.
I fixed it up (the latter removed the line modified by the former,
so I just used 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:[~2021-08-26 6:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 6:48 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-13 5:13 linux-next: manual merge of the kspp tree with the kbuild tree Stephen Rothwell
2024-05-13 18:50 ` Kees Cook
2024-05-14 0:21 ` Stephen Rothwell
2024-02-26 5:58 Stephen Rothwell
2024-02-27 2:24 ` Kees Cook
2024-03-13 22:44 ` Stephen Rothwell
2018-08-03 7:30 Stephen Rothwell
2018-08-15 23:56 ` Stephen Rothwell
2018-08-15 23:58 ` 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=20210826164809.402222af@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.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