From: patchwork-bot+netdevbpf@kernel•org
To: Saeed Mahameed <saeed@kernel•org>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
edumazet@google•com, jgg@nvidia•com, saeedm@nvidia•com,
linux-rdma@vger•kernel.org, leonro@nvidia•com,
netdev@vger•kernel.org, gregkh@linuxfoundation•org,
przemyslaw.kitszel@intel•com, parav@nvidia•com, shayd@nvidia•com
Subject: Re: [GIT PULL mlx5-next] Introduce auxiliary bus IRQs sysfs
Date: Mon, 15 Jul 2024 19:50:34 +0000 [thread overview]
Message-ID: <172107303444.9322.7675483931380584580.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240711213140.256997-1-saeed@kernel.org>
Hello:
This pull request was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Thu, 11 Jul 2024 14:31:38 -0700 you wrote:
> From: Saeed Mahameed <saeedm@nvidia•com>
>
> Hi Jakub and Greg,
>
> Following the review of v10 and Greg's request to send this via netdev.
> This is a pull request that includes the 2 patches of adding IRQs sysfs
> to aux dev subsystem based on mlx5-next tree (6.10-rc3).
>
> [...]
Here is the summary with links:
- [GIT,PULL,mlx5-next] Introduce auxiliary bus IRQs sysfs
https://git.kernel.org/netdev/net-next/c/dd3cd3ca691d
- [mlx5-next,2/2] net/mlx5: Expose SFs IRQs
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-07-15 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 21:31 [GIT PULL mlx5-next] Introduce auxiliary bus IRQs sysfs Saeed Mahameed
2024-07-11 21:31 ` [mlx5-next 1/2] driver core: auxiliary bus: show auxiliary device IRQs Saeed Mahameed
2024-07-11 21:31 ` [mlx5-next 2/2] net/mlx5: Expose SFs IRQs Saeed Mahameed
2024-07-13 22:51 ` [GIT PULL mlx5-next] Introduce auxiliary bus IRQs sysfs Jakub Kicinski
2024-07-15 17:56 ` Saeed Mahameed
2024-07-15 19:50 ` patchwork-bot+netdevbpf [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=172107303444.9322.7675483931380584580.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=jgg@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leonro@nvidia$(echo .)com \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=parav@nvidia$(echo .)com \
--cc=przemyslaw.kitszel@intel$(echo .)com \
--cc=saeed@kernel$(echo .)org \
--cc=saeedm@nvidia$(echo .)com \
--cc=shayd@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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