From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeedm@nvidia.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
leonro@nvidia.com, borisp@nvidia.com, netdev@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: adjust MELLANOX ETHERNET INNOVA DRIVERS to TLS support removal
Date: Thu, 9 Jun 2022 22:56:57 -0700 [thread overview]
Message-ID: <20220609225657.299278f7@kernel.org> (raw)
In-Reply-To: <165483841435.4442.11942577289291510346.git-patchwork-notify@kernel.org>
On Fri, 10 Jun 2022 05:20:14 +0000 patchwork-bot+netdevbpf@kernel.org
wrote:
> Hello:
>
> This patch was applied to netdev/net.git (master)
> by Saeed Mahameed <saeedm@nvidia.com>:
>
> On Wed, 1 Jun 2022 06:57:38 +0200 you wrote:
> > Commit 40379a0084c2 ("net/mlx5_fpga: Drop INNOVA TLS support") removes all
> > files in the directory drivers/net/ethernet/mellanox/mlx5/core/accel/, but
> > misses to adjust its reference in MAINTAINERS.
> >
> > Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> > broken reference.
> >
> > [...]
>
> Here is the summary with links:
> - MAINTAINERS: adjust MELLANOX ETHERNET INNOVA DRIVERS to TLS support removal
> https://git.kernel.org/netdev/net/c/ed872f92fd09
What luck. I was trying to see if pw-bot will respond to the PR rather
than the series if I mark the series as accepted first but apparently
it found this random posting and replied to it instead :S
That's a roundabout way of saying that I pulled "mlx5 fixes 2022-06-08",
thanks!
prev parent reply other threads:[~2022-06-10 5:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 4:57 [PATCH] MAINTAINERS: adjust MELLANOX ETHERNET INNOVA DRIVERS to TLS support removal Lukas Bulwahn
2022-06-01 10:18 ` Leon Romanovsky
2022-06-01 17:30 ` Jakub Kicinski
2022-06-01 18:08 ` Leon Romanovsky
2022-06-01 19:26 ` Jakub Kicinski
2022-06-02 6:13 ` Leon Romanovsky
2022-06-10 5:20 ` patchwork-bot+netdevbpf
2022-06-10 5:56 ` 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=20220609225657.299278f7@kernel.org \
--to=kuba@kernel.org \
--cc=borisp@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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;
as well as URLs for NNTP newsgroup(s).