From: "Darrick J. Wong" <djwong@kernel.org>
To: Chandan Babu R <chandanbabu@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
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,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Shirley Ma <shirley.ma@oracle.com>
Subject: Re: shmem patches headsup: Re: [ANNOUNCE] xfs-linux: for-next updated to 9ee85f235efe
Date: Wed, 14 Feb 2024 09:04:01 -0800 [thread overview]
Message-ID: <20240214170401.GA616564@frogsfrogsfrogs> (raw)
In-Reply-To: <877cj7a1zw.fsf@debian-BULLSEYE-live-builder-AMD64>
On Wed, Feb 14, 2024 at 01:51:42PM +0530, Chandan Babu R wrote:
> On Wed, Feb 14, 2024 at 09:03:05 AM +0100, 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.
> >
>
> I am sorry. I completely forgot about the requirement for an ack from the MM
> maintainers. Thanks for bringing it to notice.
These seven patches have been out for review for nineteen days.
Patches 4, 5, and 7 have been out for review for FORTY TWO DAYS.
willy reviewed them after I asked him (thank you willy!), but this kind
of lead time for fairly minor patches is unworkable.
If you two are so overworked that you cannot provide feedback in under
six weeks, then I really need you to ask your manager for more help
hiring staff so that you can delegate tasks and unburden yourselves.
Stalling everyone else is a shitty thing to do. Long feedback cycles
are destructive to developing things together -- look at what XFS has
become.
Or just let the patches go in and hch and I will deal with the
regression reports. Maybe we'll even learn a few things in the process.
Spreading knowledge around the community and decentralizing to reduce
bus factor are two key points of free software, right?
In the meantime, this is blocking me from preparing online repair pull
requests for XFS for 6.9 because those patches need the stuff at the end
of the diet-v3 series.
--D
> --
> Chandan
>
prev parent reply other threads:[~2024-02-14 17:04 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
2024-02-15 13:14 ` Matthew Wilcox
2024-02-14 8:21 ` Chandan Babu R
2024-02-14 17:04 ` Darrick J. Wong [this message]
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=20240214170401.GA616564@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chandanbabu@kernel.org \
--cc=hch@lst.de \
--cc=hughd@google.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=shirley.ma@oracle.com \
/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).