| Message ID | 1741608293-41436-1-git-send-email-tariqt@nvidia.com (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | ef4a47a8abb33d996ab6e0d5b7ad57535f37c88b |
| Headers | show |
| Series | [pull-request] mlx5-next updates 2025-03-10 | expand |
Hello: This pull request was applied to bpf/bpf-next.git (net) by Jakub Kicinski <kuba@kernel.org>: On Mon, 10 Mar 2025 14:04:53 +0200 you wrote: > Hi, > > The following pull-request contains common mlx5 updates for your *net-next* tree. > Please pull and let me know of any problem. > > Regards, > Tariq > > [...] Here is the summary with links: - [pull-request] mlx5-next updates 2025-03-10 https://git.kernel.org/bpf/bpf-next/c/ef4a47a8abb3 You are awesome, thank you!
On 11/03/2025 12:42, patchwork-bot+netdevbpf@kernel.org wrote: > Hello: > > This pull request was applied to bpf/bpf-next.git (net) Seems to be mistakenly applied to bpf-next instead of net-next. > by Jakub Kicinski <kuba@kernel.org>: > > On Mon, 10 Mar 2025 14:04:53 +0200 you wrote: >> Hi, >> >> The following pull-request contains common mlx5 updates for your *net-next* tree. >> Please pull and let me know of any problem. >> >> Regards, >> Tariq >> >> [...] > > Here is the summary with links: > - [pull-request] mlx5-next updates 2025-03-10 > https://git.kernel.org/bpf/bpf-next/c/ef4a47a8abb3 > > You are awesome, thank you!
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. In any case, the tag pulls 6 commits for me now.. (I may have missed repost, I'm quite behind on the ML traffic)
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...
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. > 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. Thanks, Paolo
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
Hi, The following pull-request contains common mlx5 updates for your *net-next* tree. Please pull and let me know of any problem. Regards, Tariq ---------------------------------------------------------------- The following changes since commit 15b103df80b25025040faa8f35164c2595977bdb: net/mlx5: fs, add RDMA TRANSPORT steering domain support (2025-03-08 13:22:49 -0500) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git mlx5-next for you to fetch changes up to f550694e88b7b13b647777f889e03e544d9db60c: net/mlx5: Add IFC bits for PPCNT recovery counters group (2025-03-10 04:31:15 -0400) ---------------------------------------------------------------- Yael Chemla (1): net/mlx5: Add IFC bits for PPCNT recovery counters group include/linux/mlx5/device.h | 1 + include/linux/mlx5/mlx5_ifc.h | 11 ++++++++++- 2 files changed, 11 insertions(+), 1 deletion(-)