[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f30ee793-6538-4ec8-b90d-90e7513a5b3c@gmail.com>
Date: Thu, 13 Mar 2025 10:07:09 +0200
From: Tariq Toukan <ttoukan.linux@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: patchwork-bot+netdevbpf@...nel.org, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, andrew+netdev@...n.ch,
leon@...nel.org, saeedm@...dia.com, gal@...dia.com, mbloch@...dia.com,
moshe@...dia.com, linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, leonro@...dia.com, ychemla@...dia.com,
Tariq Toukan <tariqt@...dia.com>
Subject: Re: [pull-request] mlx5-next updates 2025-03-10
On 12/03/2025 22:29, Jakub Kicinski wrote:
> On Tue, 11 Mar 2025 22:50:24 +0200 Tariq Toukan wrote:
>>> This pull request was applied to bpf/bpf-next.git (net)
>>
>> Seems to be mistakenly applied to bpf-next instead of net-next.
>
> The bot gets confused. You should probably throw the date into the tag
> to make its job a little easier.
It did not pull the intended patch in this PR:
f550694e88b7 net/mlx5: Add IFC bits for PPCNT recovery counters group
Anything wrong with the PR itself?
Or it is bot issue?
> In any case, the tag pulls 6 commits
> for me now.. (I may have missed repost, I'm quite behind on the ML
> traffic)
How do we get the patch pulled?
It's necessary for my next feature in queue...
Powered by blists - more mailing lists