lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a26fd105-deae-4efd-8d77-d5d9e0cac13a@gmail.com>
Date: Thu, 13 Mar 2025 11:08:08 +0200
From: Tariq Toukan <ttoukan.linux@...il.com>
To: Paolo Abeni <pabeni@...hat.com>, Jakub Kicinski <kuba@...nel.org>
Cc: patchwork-bot+netdevbpf@...nel.org, davem@...emloft.net,
 edumazet@...gle.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 13/03/2025 10:56, Paolo Abeni wrote:
> On 3/13/25 9:07 AM, Tariq Toukan wrote:
>> 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?
> 
> My [limited] understanding is as follow: nobody actually processed the
> PR yet, the bot was just confused by the generic tag name.
> 
> I can pull the tag right now/soon, if you confirm that this tag:
> 
> https://web.git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git/log/?h=mlx5-next
> 
> is still valid/correct.
> 

Yes please. Confirmed. Thank you.

>> It's necessary for my next feature in queue...
> 
> Please note that due to the concurrent NetDev conference we are
> processing patches with limited capacity, please expect considerable delay.
> 

Of course! That's totally expected.
I wouldn't nudge pulling this without the bot's weird misleading reply.

Regards,
Tariq

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ