From: Jakub Kicinski <kuba@kernel.org>
To: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Cc: patchwork-bot+netdevbpf@kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, davem@davemloft.net,
leon@kernel.org, jgg@ziepe.ca, saeedm@nvidia.com,
mbloch@nvidia.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
gal@nvidia.com, moshe@nvidia.com, ychemla@nvidia.com,
shshitrit@nvidia.com, Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [PATCH net-next] net/mlx5: Fix 1600G link mode enum naming
Date: Fri, 6 Feb 2026 18:44:56 -0800 [thread overview]
Message-ID: <20260206184456.01f46d4e@kernel.org> (raw)
In-Reply-To: <68fe9c87-c8e3-43eb-a40b-4b05267fa236@linux.intel.com>
On Fri, 6 Feb 2026 11:48:58 +0100 Dawid Osuchowski wrote:
> > Here is the summary with links:
> > - [net-next] net/mlx5: Fix 1600G link mode enum naming
> > https://git.kernel.org/netdev/net-next/c/215b53099b60
> >
> > You are awesome, thank you!
>
> Hey Kuba,
>
> I noticed that in the commit message on the net-next tree the following
> tags are duplicated:
>
> Reported-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
> Signed-off-by: Yael Chemla <ychemla@nvidia.com>
>
> Is that by design or did the bot break something? This is purely out of
> my curiosity.
Oh damn :( This is what patchwork produces:
Reported-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Signed-off-by: Yael Chemla <ychemla@nvidia.com>
Reviewed-by: Shahar Shitrit <shshitrit@nvidia.com>
Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
Reviewed-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Reported-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Signed-off-by: Yael Chemla <ychemla@nvidia.com>
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
Reported-by: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
Signed-off-by: Yael Chemla <ychemla@nvidia.com>
I fixed it up manually but clearly not well enough.
Patchwork needs so much work..
prev parent reply other threads:[~2026-02-07 2:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 19:43 [PATCH net-next] net/mlx5: Fix 1600G link mode enum naming Tariq Toukan
2026-02-04 22:39 ` Jacob Keller
2026-02-05 12:42 ` Dawid Osuchowski
2026-02-05 15:57 ` Jakub Kicinski
2026-02-05 12:54 ` Leon Romanovsky
2026-02-06 2:50 ` patchwork-bot+netdevbpf
2026-02-06 10:48 ` Dawid Osuchowski
2026-02-07 2:44 ` 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=20260206184456.01f46d4e@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dawid.osuchowski@linux.intel.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
--cc=saeedm@nvidia.com \
--cc=shshitrit@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=ychemla@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