[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200429065404.GA32139@lst.de>
Date: Wed, 29 Apr 2020 08:54:04 +0200
From: Christoph Hellwig <hch@....de>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: Christoph Hellwig <hch@....de>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Networking <netdev@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Xiaoming Ni <nixiaoming@...wei.com>,
"Guilherme G. Piccoli" <gpiccoli@...onical.com>
Subject: Re: linux-next: manual merge of the akpm-current tree with the
bpf-next tree
On Tue, Apr 28, 2020 at 11:49:34PM -0700, Alexei Starovoitov wrote:
> On Tue, Apr 28, 2020 at 11:47 PM Christoph Hellwig <hch@....de> wrote:
> >
> > On Wed, Apr 29, 2020 at 04:45:07PM +1000, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Today's linux-next merge of the akpm-current tree got a conflict in:
> > >
> > > kernel/sysctl.c
> > >
> > > between commit:
> > >
> > > f461d2dcd511 ("sysctl: avoid forward declarations")
> > >
> > > from the bpf-next tree and commits:
> >
> > Hmm, the above should have gone in through Al..
>
> Al pushed them into vfs tree and we pulled that tag into bpf-next.
Ok. And Stephen pulled your tree first.
Powered by blists - more mailing lists