netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>
Cc: patchwork-bot+netdevbpf@kernel.org, davem@davemloft.net,
	edumazet@google.com, andrew+netdev@lunn.ch, leon@kernel.org,
	saeedm@nvidia.com, gal@nvidia.com, mbloch@nvidia.com,
	moshe@nvidia.com, linux-rdma@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	leonro@nvidia.com, ychemla@nvidia.com,
	Tariq Toukan <tariqt@nvidia.com>
Subject: Re: [pull-request] mlx5-next updates 2025-03-10
Date: Thu, 13 Mar 2025 11:08:08 +0200	[thread overview]
Message-ID: <a26fd105-deae-4efd-8d77-d5d9e0cac13a@gmail.com> (raw)
In-Reply-To: <2ff2d876-84b4-4f2f-a8cc-5eeb0affed2b@redhat.com>



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

      reply	other threads:[~2025-03-13  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 12:04 [pull-request] mlx5-next updates 2025-03-10 Tariq Toukan
2025-03-11 10:42 ` patchwork-bot+netdevbpf
2025-03-11 20:50   ` Tariq Toukan
2025-03-12 20:29     ` Jakub Kicinski
2025-03-13  8:07       ` Tariq Toukan
2025-03-13  8:56         ` Paolo Abeni
2025-03-13  9:08           ` Tariq Toukan [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=a26fd105-deae-4efd-8d77-d5d9e0cac13a@gmail.com \
    --to=ttoukan.linux@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --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=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;
as well as URLs for NNTP newsgroup(s).