linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Chandan Babu R <chandanbabu@kernel.org>,
	linux-fsdevel@vger.kernel.org,  linux-xfs@vger.kernel.org,
	Hugh Dickins <hughd@google.com>,
	 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 00:18:46 -0800 (PST)	[thread overview]
Message-ID: <0e8d50e9-4254-7acc-e9b4-9b6ad63a25da@google.com> (raw)
In-Reply-To: <20240214080305.GA10568@lst.de>

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.

Hugh


  reply	other threads:[~2024-02-14  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87frxva65g.fsf@debian-BULLSEYE-live-builder-AMD64>
2024-02-14  8:03 ` Christoph Hellwig
2024-02-14  8:18   ` Hugh Dickins [this message]
2024-02-15  7:39     ` Hugh Dickins
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=0e8d50e9-4254-7acc-e9b4-9b6ad63a25da@google.com \
    --to=hughd@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=chandanbabu@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.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