From: Jakub Kicinski <kuba@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: netdev-bot+sashiko@kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, gal@nvidia.com, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, ohartoov@nvidia.com, saeedm@nvidia.com,
shayd@nvidia.com, roman.gushchin@linux.dev
Subject: Re: [PATCH net] net/mlx5: Lag, only cache max_tx_speed that FW has not accepted
Date: Thu, 8 Oct 2026 12:20:57 -0700 [thread overview]
Message-ID: <20261008122057.6314bba8@kernel.org> (raw)
In-Reply-To: <3b650188-f8f1-4d73-bde7-5ca877a9dfe9@nvidia.com>
On Thu, 8 Oct 2026 20:41:16 +0300 Tariq Toukan wrote:
> We received 3 different emails from Sashiko bots for this single patch.
> Or replied to a similar issue in another Sashiko mail, but now I see it
> wasn't the netdev one.
>
> Anyway, sorry for the delay.
Ugh, this is so annoying. The main sashiko instance insists on trimming
the CC list, so we didn't see the Sashiko.dev email or Or's reply :(
The trimming is really hugely silly, netdev patches are very often
cross-posted to other MLs.
Roman, our instance has been using the full CC list form months now
and I haven't received a single complaint (well, I have, but about
the format of the reply and its metadata, not the CC list). Please
reconsider?
prev parent reply other threads:[~2026-10-08 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 7:02 Tariq Toukan
2026-10-04 7:08 ` netdev-bot+sinfo
2026-10-05 7:42 ` netdev-bot+sashiko
2026-10-08 16:48 ` Jakub Kicinski
2026-10-08 17:41 ` Tariq Toukan
2026-10-08 19:20 ` Jakub Kicinski [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=20261008122057.6314bba8@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ohartoov@nvidia.com \
--cc=pabeni@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.com \
--cc=tariqt@nvidia.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
all inboxes | Powered by JetHome®