From: Hugh Dickins <hughd@google.com>
To: Christopn Hellwig <hch@lst.de>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Chandan Babu R <chandanbabu@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: shmem patches headsup: Re: [ANNOUNCE] xfs-linux: for-next updated to 9ee85f235efe
Date: Wed, 14 Feb 2024 23:39:06 -0800 (PST) [thread overview]
Message-ID: <38716bcd-f26b-a7f5-2ef9-1ad554d42357@google.com> (raw)
In-Reply-To: <0e8d50e9-4254-7acc-e9b4-9b6ad63a25da@google.com>
On Wed, 14 Feb 2024, Hugh Dickins wrote:
> On Wed, 14 Feb 2024, Christoph Hellwig wrote:
> > On Wed, Feb 14, 2024 at 12:18:41PM +0530, Chandan Babu R wrote:
> > > The for-next branch of the xfs-linux repository at:
> > >
> > > https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
> > >
> > > has just been updated.
> >
> > <snip>
> >
> > > Christoph Hellwig (17):
> > > [f23e079e024c] mm: move mapping_set_update out of <linux/swap.h>
> > > [604ee858a8c8] shmem: move shmem_mapping out of line
> > > [8481cd645af6] shmem: set a_ops earlier in shmem_symlink
> > > [9b4ec2cf0154] shmem: move the shmem_mapping assert into shmem_get_folio_gfp
> > > [36e3263c623a] shmem: export shmem_get_folio
> > > [74f6fd19195a] shmem: export shmem_kernel_file_setup
> > > [eb84b86441e3] shmem: document how to "persist" data when using shmem_*file_setup
> >
> > I would have prefer an ACK or even a shared branch in the MM tree
> > for these. But as it's been impossible to get any feedback from
> > the shmem and mm maintainer maybe this is the right thing to do.
> >
> > Andrew, Hugh: can you commet if this is ok?
>
> Each day I hope to reach looking at it. I sincerely believed that
> I would get to it yesterday, but no. Later on today? We shall see.
Christoph, I'd better give you a progress report, to avoid another mail
as foul as was sent after yours.
I wonder what the fuss is: Matthew (thank you) has been giving excellent
reviews, and mm is a cooperative not a dickinstatorship (but I was upset
that he caught that GFP_HIGHUSER, which I had been eager to point out).
I haven't finished yet, but made good progress and it does look good:
a few very minor comments so far, nothing that couldn't be patched up
later if that suits you best.
mm.git contains no updates to mm/shmem.c yet this cycle, so I expect
that Andrew will be fine with the series going in via the XFS tree,
unless some awkward conflict in one of the mm files appears.
Tomorrow,
Hugh
next prev parent reply other threads:[~2024-02-15 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 6:48 [ANNOUNCE] xfs-linux: for-next updated to 9ee85f235efe Chandan Babu R
2024-02-14 8:03 ` shmem patches headsup: " Christoph Hellwig
2024-02-14 8:18 ` Hugh Dickins
2024-02-15 7:39 ` Hugh Dickins [this message]
2024-02-15 13:14 ` Matthew Wilcox
2024-02-14 8:21 ` Chandan Babu R
2024-02-14 17:04 ` Darrick J. Wong
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=38716bcd-f26b-a7f5-2ef9-1ad554d42357@google.com \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=chandanbabu@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.org \
/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).