From: patchwork-bot+netdevbpf@kernel.org
To: Mark Gray <mark.d.gray@redhat.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org, pshelar@ovn.org,
davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net-next 0/3] openvswitch: per-cpu upcall patchwork issues
Date: Tue, 27 Jul 2021 11:00:28 +0000 [thread overview]
Message-ID: <162738362825.18831.11702364143818289111.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210723142414.55267-1-mark.d.gray@redhat.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 23 Jul 2021 10:24:11 -0400 you wrote:
> Some issues were raised by patchwork at:
> https://patchwork.kernel.org/project/netdevbpf/patch/20210630095350.817785-1-mark.d.gray@redhat.com/#24285159
>
> Mark Gray (3):
> openvswitch: update kdoc OVS_DP_ATTR_PER_CPU_PIDS
> openvswitch: fix alignment issues
> openvswitch: fix sparse warning incorrect type
>
> [...]
Here is the summary with links:
- [net-next,1/3] openvswitch: update kdoc OVS_DP_ATTR_PER_CPU_PIDS
https://git.kernel.org/netdev/net-next/c/e4252cb66637
- [net-next,2/3] openvswitch: fix alignment issues
https://git.kernel.org/netdev/net-next/c/784dcfa56e04
- [net-next,3/3] openvswitch: fix sparse warning incorrect type
https://git.kernel.org/netdev/net-next/c/076999e46027
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:[~2021-07-27 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 14:24 [PATCH net-next 0/3] openvswitch: per-cpu upcall patchwork issues Mark Gray
2021-07-23 14:24 ` [PATCH net-next 1/3] openvswitch: update kdoc OVS_DP_ATTR_PER_CPU_PIDS Mark Gray
2021-07-23 14:24 ` [PATCH net-next 2/3] openvswitch: fix alignment issues Mark Gray
2021-07-23 14:24 ` [PATCH net-next 3/3] openvswitch: fix sparse warning incorrect type Mark Gray
2021-07-27 11:00 ` 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=162738362825.18831.11702364143818289111.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=kuba@kernel.org \
--cc=mark.d.gray@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.