From: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Ravi Gunasekaran <r-gunasekaran@ti.com>,
Roger Quadros <rogerq@kernel.org>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH net-next] net: ethernet: ti: cpsw: flower: validate control flags
Date: Tue, 23 Apr 2024 15:31:39 +0000 [thread overview]
Message-ID: <a8238354-c36e-4dcb-88ba-1417adc44245@fiberby.net> (raw)
In-Reply-To: <ZiewT6N2fjhFwrpW@nanopsycho>
Hi Jiri,
Thank you for the reviews.
On 4/23/24 12:57 PM, Jiri Pirko wrote:
> Next time, could you please bundle similar/related patches into
> a patchset?
Sure, I did it per driver to make it easier to handle differences in
get_maintainer output and be able to integrate feedback into later patches
for other drivers, and since the patches could be applied individually.
When I started I through that more drivers had their own trees, wasn't
aware that it was only Intel, and that mlx5-next was dead.
For instance the feedback from Jianbo on mlx5 patch, also went into the
octeontx2-pf patch.
I only have one patch left in the queue now (for qede).
--
Best regards
Asbjørn Sloth Tønnesen
Network Engineer
Fiberby - AS42541
next prev parent reply other threads:[~2024-04-23 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 15:26 [PATCH net-next] net: ethernet: ti: cpsw: flower: validate control flags Asbjørn Sloth Tønnesen
2024-04-23 12:57 ` Jiri Pirko
2024-04-23 15:31 ` Asbjørn Sloth Tønnesen [this message]
2024-04-25 3:00 ` 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=a8238354-c36e-4dcb-88ba-1417adc44245@fiberby.net \
--to=ast@fiberby.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.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 read-only IMAP folder(s) and NNTP newsgroup(s).