devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Sean Anderson <sean.anderson@seco.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, Camelia Groza <camelia.groza@nxp.com>,
	open list <linux-kernel@vger.kernel.org>,
	Madalin Bucur <madalin.bucur@nxp.com>,
	linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Li Yang <leoyang.li@nxp.com>, Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [RESEND PATCH net-next v4 00/25] net: dpaa: Cleanups in preparation for phylink conversion
Date: Thu, 18 Aug 2022 11:58:15 -0700	[thread overview]
Message-ID: <20220818115815.72809e33@kernel.org> (raw)
In-Reply-To: <f085609c-24c9-a9fb-e714-18ba7f3ef48a@seco.com>

On Thu, 18 Aug 2022 14:37:23 -0400 Sean Anderson wrote:
> On 8/18/22 2:20 PM, Jakub Kicinski wrote:
> > On Thu, 18 Aug 2022 12:16:24 -0400 Sean Anderson wrote:  
> >> This series contains several cleanup patches for dpaa/fman. While they
> >> are intended to prepare for a phylink conversion, they stand on their
> >> own. This series was originally submitted as part of [1].  
> > 
> > Still over the limit of patches in a patch series, and looks pretty
> > easy to chunk up. We review and apply patches in netdev in 1-3 days,
> > it really is more efficient to post smaller series.   
> 
> Last time I offered to arbitrarily chunk things [1], but I did not receive
> a response for 3 weeks.

I sent you the link to the rules. Admittedly not the most polite and
clear feedback to put it mildly but that was the reason.

> > And with the other series you sent to the list we have nearly 50
> > patches from you queued for review. I don't think this is reasonable,
> > people reviewing this code are all volunteers trying to get their
> > work done as well :(  
> 
> These patches have been sent to the list in one form or another since
> I first sent out an RFC for DPAA conversion back in June [2]. I have not
> substantially modified any of them (although I did add a few more
> since v2). It's not like I came up with these just now; I have been
> seeking feedback on these series for 2-3 months so far. The only
> reviews I have gotten were from Camelia Groza, who has provided some
> helpful feedback.

Ack, no question. I'm trying to tell you got to actually get stuff in.
It's the first week after the merge window and people are dumping code
the had written over the dead time on the list, while some reviewers
and maintainers are still on their summer vacation. So being
considerate is even more important than normally.

  reply	other threads:[~2022-08-18 18:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 16:16 [RESEND PATCH net-next v4 00/25] net: dpaa: Cleanups in preparation for phylink conversion Sean Anderson
2022-08-18 16:16 ` [RESEND PATCH net-next v4 01/25] dt-bindings: net: Convert FMan MAC bindings to yaml Sean Anderson
2022-08-18 18:20 ` [RESEND PATCH net-next v4 00/25] net: dpaa: Cleanups in preparation for phylink conversion Jakub Kicinski
2022-08-18 18:37   ` Sean Anderson
2022-08-18 18:58     ` Jakub Kicinski [this message]
2022-08-18 19:14       ` Sean Anderson
2022-08-18 19:28         ` Jakub Kicinski
2022-09-02 21:32           ` Sean Anderson
2022-09-02 21:51             ` Sean Anderson
2022-08-19 23:50 ` patchwork-bot+netdevbpf

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=20220818115815.72809e33@kernel.org \
    --to=kuba@kernel.org \
    --cc=camelia.groza@nxp.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madalin.bucur@nxp.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@kernel.org \
    --cc=sean.anderson@seco.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).