From: Andrew Lunn <andrew@lunn.ch>
To: Sergey Shtylyov <s.shtylyov@omp.ru>
Cc: patchwork-bot+netdevbpf@kernel.org,
Biju Das <biju.das.jz@bp.renesas.com>,
davem@davemloft.net, kuba@kernel.org, sergei.shtylyov@gmail.com,
geert+renesas@glider.be, s.shtylyov@omprussia.ru,
aford173@gmail.com, ashiduka@fujitsu.com,
yoshihiro.shimoda.uh@renesas.com, yangyingliang@huawei.com,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Chris.Paterson2@renesas.com, biju.das@bp.renesas.com,
prabhakar.mahadev-lad.rj@bp.renesas.com
Subject: Re: [PATCH net-next v3 0/9] Add Gigabit Ethernet driver support
Date: Thu, 19 Aug 2021 17:29:35 +0200 [thread overview]
Message-ID: <YR5435p8EE5ORQXT@lunn.ch> (raw)
In-Reply-To: <9b060154-aed4-1e11-68ac-6468e5f4f136@omp.ru>
> Are we in such a haste? I was just going to review these patches
> today...
I guess the thinking is, fixup patches can always be applied after the
fact. But i agree, i really liked the 3 day wait time for patches to
be merged, it gave a reasonable amount of time for reviews, without
slowing down development work. The current 1 day or less does seem
counter productive, i expect there are less reviews happening as a
result, lower quality code, more bugs...
Andrew
prev parent reply other threads:[~2021-08-19 15:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 19:07 [PATCH net-next v3 0/9] Add Gigabit Ethernet driver support Biju Das
2021-08-18 19:07 ` [PATCH net-next v3 1/9] ravb: Use unsigned int for num_tx_desc variable in struct ravb_private Biju Das
2021-08-19 15:26 ` Sergey Shtylyov
2021-08-18 19:07 ` [PATCH net-next v3 2/9] ravb: Add struct ravb_hw_info to driver data Biju Das
2021-08-19 16:19 ` Sergey Shtylyov
2021-08-19 17:33 ` Biju Das
2021-08-20 18:15 ` Sergey Shtylyov
2021-08-18 19:07 ` [PATCH net-next v3 3/9] ravb: Add aligned_tx to struct ravb_hw_info Biju Das
2021-08-19 15:41 ` Sergei Shtylyov
2021-08-19 15:43 ` Sergey Shtylyov
2021-08-23 9:14 ` Geert Uytterhoeven
2021-08-23 9:26 ` Biju Das
2021-08-18 19:07 ` [PATCH net-next v3 4/9] ravb: Add max_rx_len " Biju Das
2021-08-19 16:29 ` Sergey Shtylyov
2021-08-18 19:07 ` [PATCH net-next v3 5/9] ravb: Add stats_len " Biju Das
2021-08-19 16:42 ` Sergey Shtylyov
2021-08-18 19:07 ` [PATCH net-next v3 6/9] ravb: Add gstrings_stats and gstrings_size " Biju Das
2021-08-18 19:07 ` [PATCH net-next v3 7/9] ravb: Add net_features and net_hw_features " Biju Das
2021-08-18 19:07 ` [PATCH net-next v3 8/9] ravb: Add internal delay hw feature " Biju Das
2021-08-18 19:08 ` [PATCH net-next v3 9/9] ravb: Add tx_counters " Biju Das
2021-08-19 16:57 ` Sergey Shtylyov
2021-08-19 11:10 ` [PATCH net-next v3 0/9] Add Gigabit Ethernet driver support patchwork-bot+netdevbpf
2021-08-19 15:08 ` Sergey Shtylyov
2021-08-19 15:29 ` Andrew Lunn [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=YR5435p8EE5ORQXT@lunn.ch \
--to=andrew@lunn.ch \
--cc=Chris.Paterson2@renesas.com \
--cc=aford173@gmail.com \
--cc=ashiduka@fujitsu.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=s.shtylyov@omp.ru \
--cc=s.shtylyov@omprussia.ru \
--cc=sergei.shtylyov@gmail.com \
--cc=yangyingliang@huawei.com \
--cc=yoshihiro.shimoda.uh@renesas.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).