From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>,
Christian Brauner <christian@brauner•io>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
"Joel Fernandes (Google)" <joel@joelfernandes•org>
Subject: Re: linux-next: manual merge of the akpm-current tree with the pidfd tree
Date: Tue, 9 Jul 2019 09:12:36 +1000 [thread overview]
Message-ID: <20190709091236.3b658262@canb.auug.org.au> (raw)
In-Reply-To: <20190522114314.515b410d@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
Hi all,
On Wed, 22 May 2019 11:43:14 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the akpm-current tree got a conflict in:
>
> kernel/pid.c
>
> between commit:
>
> 99e9da7f2796 ("pid: add pidfd_open()")
>
> from the pidfd tree and commit:
>
> 51c59c914840 ("kernel/pid.c: convert struct pid:count to refcount_t")
>
> 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 kernel/pid.c
> index 39181ccca846,b59681973dd6..000000000000
> --- a/kernel/pid.c
> +++ b/kernel/pid.c
> @@@ -37,8 -36,7 +37,8 @@@
> #include <linux/init_task.h>
> #include <linux/syscalls.h>
> #include <linux/proc_ns.h>
> - #include <linux/proc_fs.h>
> + #include <linux/refcount.h>
> +#include <linux/sched/signal.h>
> #include <linux/sched/task.h>
> #include <linux/idr.h>
>
I am still getting this conflict. Just a reminder in case you think
Linus may need to know.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-08 23:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 1:43 linux-next: manual merge of the akpm-current tree with the pidfd tree Stephen Rothwell
2019-05-24 8:15 ` Joel Fernandes
2019-07-08 23:12 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-27 11:43 Stephen Rothwell
2021-01-28 2:04 ` Miaohe Lin
2021-02-14 21:54 ` Stephen Rothwell
2021-02-24 22:41 ` Stephen Rothwell
2020-09-22 8:54 Stephen Rothwell
2019-05-15 3:16 Stephen Rothwell
2019-07-08 2:01 ` Stephen Rothwell
2019-07-12 12:53 ` Joel Fernandes
2019-07-12 13:02 ` Christian Brauner
2019-07-12 13:54 ` Joel Fernandes
2019-04-23 8:46 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=20190709091236.3b658262@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=christian@brauner$(echo .)io \
--cc=joel@joelfernandes$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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