From: Christoph Hellwig <hch@infradead.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>, linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to f259584cb40c
Date: Fri, 27 Jun 2025 06:21:24 -0700 [thread overview]
Message-ID: <aF6a1GhCdT_llDSm@infradead.org> (raw)
In-Reply-To: <k2jkeacuav6orgxae3sflzgeszc2wfmffjhhu5okjulkglcnvn@2gyui2k6htql>
On Fri, Jun 27, 2025 at 03:13:55PM +0200, Carlos Maiolino wrote:
> On Fri, Jun 27, 2025 at 05:58:08AM -0700, Christoph Hellwig wrote:
> > Btw, I assumed you'd send my fixes from three weeks ago to Linus for
> > 6.16. Do you plan to wait for 6.17 or did you just not get around
> > sending a pull request? At least for the zone allocator shutdown
> > check that would be annoying as it causes hangs during testing.
> >
>
> You meant the ones we already have in for-next?
Yes.
> I'll send them for 6.16,
Awesome, I kjust wanted to double check.
> I'm planning to send everything we have now in for-next to Linus on next
> week. I can send a pull tomorrow with things already staged for a few
> days (i.e. without the patches from today) if you need it urgently, but
> I'd rather wait to send it to -rc5 if that's ok with you.
In general I'd like to see them out rather sooner than later, but
if it's easier for your it can wait.
prev parent reply other threads:[~2025-06-27 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 12:55 [ANNOUNCE] xfs-linux: for-next updated to f259584cb40c Carlos Maiolino
2025-06-27 12:58 ` Christoph Hellwig
2025-06-27 13:13 ` Carlos Maiolino
2025-06-27 13:21 ` Christoph Hellwig [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=aF6a1GhCdT_llDSm@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.