From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [5.19 cycle] Planning and goals
Date: Mon, 11 Apr 2022 11:51:25 +1000 [thread overview]
Message-ID: <20220411015125.GW1544202@dread.disaster.area> (raw)
In-Reply-To: <20220410182112.GA14125@magnolia>
On Sun, Apr 10, 2022 at 11:21:12AM -0700, Darrick J. Wong wrote:
> On Thu, Apr 07, 2022 at 03:49:39PM +1000, Dave Chinner wrote:
> > On Wed, Apr 06, 2022 at 08:11:06PM -0700, Darrick J. Wong wrote:
> > > On Tue, Apr 05, 2022 at 12:03:12PM +1000, Dave Chinner wrote:
> > > > Have I missed any of the major outstanding things that are nearly
> > > > ready to go?
> > >
> > > At this point my rmap/reflink performance speedups series are ready for
> > > review,
> >
> > OK, what's the timeframe for you getting them out for review? Today,
> > next week, -rc4?
>
> I'll send them as soon as the frextents bugfix series clears review.
Thanks!
> > Speaking as the "merge shepherd" for this release, what I want from
> > this discussion is feedback that points out things I've missed, for
> > the authors of patchsets that I've flagged as merge candidates to
> > tell me if they are able to do the work needed in the next 4-6 weeks
> > to get their work merged, for people to voice their concerns about
> > aspects of the plan, etc.
>
> <nod> I hope you've gotten enough info to proceed, then?
Yes, so far, so good :)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2022-04-11 1:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 2:03 [5.19 cycle] Planning and goals Dave Chinner
2022-04-07 3:11 ` Darrick J. Wong
2022-04-07 5:49 ` Dave Chinner
2022-04-07 22:40 ` Alli
2022-04-11 1:50 ` Dave Chinner
2022-04-11 3:59 ` Dave Chinner
2022-04-11 7:31 ` Dave Chinner
2022-04-11 8:50 ` Dave Chinner
2022-04-11 20:00 ` Alli
2022-04-11 19:38 ` Alli
2022-04-10 18:21 ` Darrick J. Wong
2022-04-11 1:51 ` Dave Chinner [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=20220411015125.GW1544202@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox