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

I am disappointed with how little content is making it into 5.10


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.


Tom


             reply	other threads:[~2020-09-14 20:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 20:29 Tom Rix [this message]
2020-09-14 21:10 ` RFC improving amount of content in 5.11 Moritz Fischer
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=3295710c-5e82-7b97-43de-99b9870a8c8c@redhat.com \
    --to=trix@redhat.com \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=mdf@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;
as well as URLs for NNTP newsgroup(s).