From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kees Cook <keescook@google.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: linux-next: manual merge of the kspp tree with the kbuild tree
Date: Thu, 16 Aug 2018 09:56:28 +1000 [thread overview]
Message-ID: <20180816095628.686cba3a@canb.auug.org.au> (raw)
In-Reply-To: <20180803173020.6ec4014b@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
Hi all,
On Fri, 3 Aug 2018 17:30:20 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the kspp tree got a conflict in:
>
> arch/Kconfig
>
> between commit:
>
> 22471e1313f2 ("kconfig: use a menu in arch/Kconfig to reduce clutter")
>
> from the kbuild tree and commit:
>
> 45332b1bdfdc ("gcc-plugins: split out Kconfig entries to scripts/gcc-plugins/Kconfig")
>
> from the kspp 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/Kconfig
> index 6cf1b17a8df2,43f315b84c8f..000000000000
> --- a/arch/Kconfig
> +++ b/arch/Kconfig
> @@@ -984,4 -836,4 +847,6 @@@ config REFCOUNT_FUL
>
> source "kernel/gcov/Kconfig"
>
> + source "scripts/gcc-plugins/Kconfig"
> ++
> +endmenu
This is now a conflict between Linus' tree and the kspp tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-15 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 7:30 linux-next: manual merge of the kspp tree with the kbuild tree Stephen Rothwell
2018-08-15 23:56 ` Stephen Rothwell [this message]
2018-08-15 23:58 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-08-26 6:48 Stephen Rothwell
2024-02-26 5:58 Stephen Rothwell
2024-02-27 2:24 ` Kees Cook
2024-03-13 22:44 ` Stephen Rothwell
2024-05-13 5:13 Stephen Rothwell
2024-05-13 18:50 ` Kees Cook
2024-05-14 0:21 ` 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=20180816095628.686cba3a@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=rdunlap@infradead.org \
--cc=yamada.masahiro@socionext.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