From: patchwork-bot+netdevbpf@kernel•org
To: Tariq Toukan <tariqt@nvidia•com>
Cc: stephen@networkplumber•org, dsahern@kernel•org,
davem@davemloft•net, edumazet@google•com, pabeni@redhat•com,
jiri@nvidia•com, dchumak@nvidia•com, kuba@kernel•org,
leonro@nvidia•com, saeedm@nvidia•com, netdev@vger•kernel.org
Subject: Re: [PATCH iproute2-next V3 0/2] devlink: Add port function attributes for ipsec
Date: Wed, 04 Oct 2023 15:30:26 +0000 [thread overview]
Message-ID: <169643342696.21372.15580194782521448329.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231002104349.971927-1-tariqt@nvidia.com>
Hello:
This series was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel•org>:
On Mon, 2 Oct 2023 13:43:47 +0300 you wrote:
> Hi,
> Please, see kernel series [1] for the overview of these changes.
>
> [1] https://lore.kernel.org/netdev/20230825062836.103744-1-saeed@kernel.org/
>
> Regards,
> Tariq
>
> [...]
Here is the summary with links:
- [iproute2-next,V3,1/2] devlink: Support setting port function ipsec_crypto cap
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=27fd1bfa1b5f
- [iproute2-next,V3,2/2] devlink: Support setting port function ipsec_packet cap
https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=994e80e9c9fb
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:[~2023-10-04 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 10:43 [PATCH iproute2-next V3 0/2] devlink: Add port function attributes for ipsec Tariq Toukan
2023-10-02 10:43 ` [PATCH iproute2-next V3 1/2] devlink: Support setting port function ipsec_crypto cap Tariq Toukan
2023-10-03 14:46 ` David Ahern
2023-10-03 18:05 ` Leon Romanovsky
2023-10-02 10:43 ` [PATCH iproute2-next V3 2/2] devlink: Support setting port function ipsec_packet cap Tariq Toukan
2023-10-04 15:30 ` 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=169643342696.21372.15580194782521448329.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dchumak@nvidia$(echo .)com \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=jiri@nvidia$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leonro@nvidia$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=tariqt@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