From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
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>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: manual merge of the akpm-current tree with the kbuild tree
Date: Thu, 16 Aug 2018 09:55:30 +1000 [thread overview]
Message-ID: <20180816095530.5b3c9ecb@canb.auug.org.au> (raw)
In-Reply-To: <20180803183653.4d394bcf@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 2414 bytes --]
Hi all,
On Fri, 3 Aug 2018 18:36:53 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> lib/Kconfig.debug
>
> between commit:
>
> 06ec64b84c35 ("Kconfig: consolidate the "Kernel hacking" menu")
>
> from the kbuild tree and commit:
>
> bbd89226bb66 ("fs/buffer.c: add debug print for __getblk_gfp() stall problem")
>
> from the akpm-current 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 lib/Kconfig.debug
> index 46f755a60872,01ec99f1cf2e..000000000000
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@@ -1729,10 -1713,9 +1727,9 @@@ config KPROBES_SANITY_TES
> bool "Kprobes sanity tests"
> depends on DEBUG_KERNEL
> depends on KPROBES
> - default n
> help
> This option provides for testing basic kprobes functionality on
> - boot. A sample kprobe, jprobe and kretprobe are inserted and
> + boot. Samples of kprobe and kretprobe are inserted and
> verified for functionality.
>
> Say N if you are unsure.
> @@@ -1851,12 -1820,8 +1844,11 @@@ config TEST_HAS
> This is intended to help people writing architecture-specific
> optimized versions. If unsure, say N.
>
> +config TEST_IDA
> + tristate "Perform selftest on IDA functions"
> +
> config TEST_PARMAN
> tristate "Perform selftest on priority array manager"
> - default n
> depends on PARMAN
> help
> Enable this option to test priority array manager on boot
> @@@ -2062,6 -2018,8 +2045,12 @@@ config IO_STRICT_DEVME
>
> If in doubt, say Y.
>
> + config DEBUG_AID_FOR_SYZBOT
> + bool "Additional debug code for syzbot"
> + default n
> + help
> + This option is intended for testing by syzbot.
> ++
> +source "arch/$(SRCARCH)/Kconfig.debug"
> +
> +endmenu # Kernel hacking
This is now a conflict between Linus' tree and the akpm-current 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:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 8:36 linux-next: manual merge of the akpm-current tree with the kbuild tree Stephen Rothwell
2018-08-15 23:55 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-08 10:34 Stephen Rothwell
2021-04-08 10:36 ` Stephen Rothwell
2020-05-11 8:23 Stephen Rothwell
2017-11-02 7:13 Stephen Rothwell
2016-01-06 6:54 Stephen Rothwell
2016-01-06 8:07 ` Michal Marek
2013-11-07 6:37 Stephen Rothwell
2013-11-07 9:49 ` Michal Marek
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=20180816095530.5b3c9ecb@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--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;
as well as URLs for NNTP newsgroup(s).