linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Moritz Fischer <mdf@kernel.org>
To: Tom Rix <trix@redhat.com>
Cc: "mdf@kernel.org" <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
	"linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>
Subject: Re: RFC improving amount of content in 5.11
Date: Mon, 14 Sep 2020 14:10:12 -0700	[thread overview]
Message-ID: <20200914211012.GA22855@archbook> (raw)
In-Reply-To: <3295710c-5e82-7b97-43de-99b9870a8c8c@redhat.com>

Hi Tom,

On Mon, Sep 14, 2020 at 01:29:47PM -0700, Tom Rix wrote:
> I am disappointed with how little content is making it into 5.10

One comment I've gotten from Greg in the past is to not hold on to
patches so long, so the pull request this weekend was me trying to a
first set of changes out there. This doesn't mean it has to be the only
content that goes into 5.10 (Note how the pull request said: "First set
of changes for the 5.10 merge window").

> So I was wondering what we can do generally and i can do specifically
> to improve this.
> 
> My comment
> Though we are a low volume list, anything non trivial takes about 8 revisions.
> My suggestion is that we all try to give the developer our big first
> pass review within a week of the patch landing and try to cut the
> revisions down to 3.

It's unfortunate that it takes so long to get things moving, I agree,
but with everything that's going on - bear in mind people deal different
with situations like the present - it is what it is.

My current dayjob doesn't pay me for working on this so the time I dedicate
to this comes out of my spare time and weekends - Personally I'd rather
not burn out and keep functioning in the long run.

Thanks,
Moritz

  reply	other threads:[~2020-09-14 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 20:29 RFC improving amount of content in 5.11 Tom Rix
2020-09-14 21:10 ` Moritz Fischer [this message]
2020-09-15 20:58   ` Tom Rix
2020-09-15 21:33     ` Moritz Fischer
2020-09-16 15:07       ` Tom Rix
2020-09-17  6:01         ` Moritz Fischer
2020-09-17 15:38           ` Tom Rix

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=20200914211012.GA22855@archbook \
    --to=mdf@kernel.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=trix@redhat.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).