[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKFNMomq1Cd2oqdM2wZQjWGcKfNCSGRgDe31uN1tX0G9tB8iuQ@mail.gmail.com>
Date: Fri, 13 May 2022 01:13:24 +0900
From: Ryusuke Konishi <konishi.ryusuke@...il.com>
To: Matthew Wilcox <willy@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Yang Li <yang.lee@...ux.alibaba.com>
Subject: Re: linux-next: manual merge of the mm tree with the folio tree
On Thu, May 12, 2022 at 9:51 PM Matthew Wilcox <willy@...radead.org> wrote:
>
> On Thu, May 12, 2022 at 08:52:17PM +0900, Ryusuke Konishi wrote:
> > On Thu, May 12, 2022 at 5:26 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > >
> > > Hi all,
> > >
> > > Today's linux-next merge of the mm tree got a conflict in:
> > >
> > > fs/nilfs2/inode.c
> > >
> > > between commit:
> > >
> > > f132ab7d3ab0 ("fs: Convert mpage_readpage to mpage_read_folio")
> > >
> > > from the folio tree and commit:
> > >
> > > e38ed506c42f ("nilfs2: Fix some kernel-doc comments")
> > >
> > > from the mm 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.
> >
> > Thanks, Stephen.
> >
> > Andrew, please once drop
> >
> > e38ed506c42f ("nilfs2: Fix some kernel-doc comments")
> >
> > from -mm tree. I will resend a modified patch after the folio patch is merged
> > to the mainline.
>
> I'd be happy to take this patch through my tree instead, if you point me
> to where I can pick it up (I don't see it on fsdevel or mm).
Thank you for your suggestion. The patch I signed is below,
https://lkml.kernel.org/r/1652276316-7791-1-git-send-email-konishi.ryusuke@gmail.com
but I guess it's better to pick up Andrew's, which seems to have been
sent to you
additionally a while ago, if it's OK for Andrew as well.
Regards,
Ryusuke Konishi
Powered by blists - more mailing lists