All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: davem@davemloft.net, abeni@redhat.com, edumazet@google.com,
	dsahern@kernel.org, weiwan@google.com,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH net-next 00/22] Fix MODULE_DESCRIPTION() for net (p2)
Date: Tue, 23 Jan 2024 08:35:17 -0800	[thread overview]
Message-ID: <20240123083517.2982c483@kernel.org> (raw)
In-Reply-To: <Za/oeIjnMoqqp4Tt@gmail.com>

On Tue, 23 Jan 2024 08:25:28 -0800 Breno Leitao wrote:
> > When you repost:
> >  - please send these 3 to linux-wireless as a separate series
> >  - make sure mailing lists are CCed on the cover letter
> >    (yes, get_maintainer is embarrassingly bad at its job)
> >  - please send 10 at-a-time, it's probably a good tradeoff
> >    between series size and reposting risk
> >  - please target net, I hope I convinced Paolo that it's okay :)  
> 
> Sure. I will split this series in 3 and target `net`.

The wireless ones need to target wireless, just to be clear.
The rest should fit into 2 series.

> I suppose it is OK to send the patchsets in parallel, instead of waiting
> for the first patchset to be reviewed/accepted before sending the second
> part. Is this correct?

The rate limit is to avoid having to give the same feedback to multiple
series, among other things. it'd be better to send one part at a time..
it won't take that long :)

  reply	other threads:[~2024-01-23 16:35 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240122184543.2501493-1-leitao@debian.org>
2024-01-22 18:45 ` [PATCH net-next 01/22] net: fill in MODULE_DESCRIPTION()s for 8390 Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 02/22] net: fill in MODULE_DESCRIPTION()s for ieee802154 Breno Leitao
2024-01-24 16:51   ` Miquel Raynal
2024-01-25 10:01     ` Breno Leitao
2024-01-25 14:55       ` Miquel Raynal
2024-01-25 15:36         ` Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 03/22] net: fill in MODULE_DESCRIPTION()s for PCS Layer Breno Leitao
2024-01-22 18:45   ` Breno Leitao
2024-01-22 19:31   ` Daniel Golle
2024-01-22 19:31     ` Daniel Golle
2024-01-22 19:42     ` Breno Leitao
2024-01-22 19:42       ` Breno Leitao
2024-01-22 19:33   ` Andrew Lunn
2024-01-22 19:33     ` Andrew Lunn
2024-01-22 19:42     ` Breno Leitao
2024-01-22 19:42       ` Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 04/22] net: fill in MODULE_DESCRIPTION()s for Broadcom bgmac Breno Leitao
2024-01-22 18:50   ` Florian Fainelli
2024-01-22 19:01     ` Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 05/22] net: fill in MODULE_DESCRIPTION()s for liquidio Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 06/22] net: fill in MODULE_DESCRIPTION()s for ep93xxx_eth Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 07/22] net: fill in MODULE_DESCRIPTION()s for nps_enet Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 08/22] net: fill in MODULE_DESCRIPTION()s for enetc Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 09/22] net: fill in MODULE_DESCRIPTION()s for fec Breno Leitao
2024-01-23  1:33   ` Wei Fang
2024-01-22 18:45 ` [PATCH net-next 10/22] net: fill in MODULE_DESCRIPTION()s for fsl_pq_mdio Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 11/22] net: fill in MODULE_DESCRIPTION()s for litex Breno Leitao
2024-01-22 20:48   ` Gabriel L. Somlo
2024-01-22 18:45 ` [PATCH net-next 12/22] net: fill in MODULE_DESCRIPTION()s for rvu_mbox Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 13/22] net: fill in MODULE_DESCRIPTION()s for encx24j600 Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 14/22] net: fill in MODULE_DESCRIPTION()s for ocelot Breno Leitao
2024-01-23  7:40   ` Horatiu Vultur
2024-01-23  7:48   ` Alexandre Belloni
2024-01-23 15:42     ` Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 15/22] net: fill in MODULE_DESCRIPTION()s for SMSC drivers Breno Leitao
2024-01-28 14:58   ` Andy Shevchenko
2024-01-22 18:45 ` [PATCH net-next 16/22] net: fill in MODULE_DESCRIPTION()s for Qualcom drivers Breno Leitao
2024-01-22 19:35   ` Subash Abhinov Kasiviswanathan (KS)
2024-01-22 18:45 ` [PATCH net-next 17/22] net: fill in MODULE_DESCRIPTION()s for Broadcom WLAN Breno Leitao
2024-01-23  6:38   ` Kalle Valo
2024-01-27  8:26     ` Arend van Spriel
2024-01-29  9:12       ` Breno Leitao
2024-01-23 11:47   ` Kalle Valo
2024-01-22 18:45 ` [PATCH net-next 18/22] net: fill in MODULE_DESCRIPTION()s for wlcore Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 19/22] net: fill in MODULE_DESCRIPTION()s for wl1251 and wl12xx Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 20/22] net: fill in MODULE_DESCRIPTION()s for dwmac-socfpga Breno Leitao
2024-01-22 18:45   ` Breno Leitao
2024-01-22 18:45 ` [PATCH net-next 21/22] net: fill in MODULE_DESCRIPTION()s for cpsw-common Breno Leitao
2024-01-23  9:50   ` Roger Quadros
2024-01-22 18:45 ` [PATCH net-next 22/22] net: fill in MODULE_DESCRIPTION()s for ec_bhf Breno Leitao
2024-01-22 18:57 ` [PATCH net-next 00/22] Fix MODULE_DESCRIPTION() for net (p2) Jakub Kicinski
2024-01-23 16:25   ` Breno Leitao
2024-01-23 16:35     ` Jakub Kicinski [this message]
2024-01-23 17:05       ` Breno Leitao

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=20240123083517.2982c483@kernel.org \
    --to=kuba@kernel.org \
    --cc=abeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=leitao@debian.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=weiwan@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.