From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, kuni1840@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v1 net-next 0/2] raw: Fix nits of RCU conversion series.
Date: Mon, 20 Jun 2022 08:20:27 +0000 [thread overview]
Message-ID: <165571322792.28545.587082097048401953.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220619232927.54259-1-kuniyu@amazon.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 19 Jun 2022 16:29:25 -0700 you wrote:
> The first patch fixes a build error by commit ba44f8182ec2 ("raw: use
> more conventional iterators"), but it does not land in the net tree,
> so this series is targeted to net-next. The second patch replaces some
> hlist functions with sk's helper macros.
>
>
> Kuniyuki Iwashima (2):
> raw: Fix mixed declarations error in raw_icmp_error().
> raw: Use helpers for the hlist_nulls variant.
>
> [...]
Here is the summary with links:
- [v1,net-next,1/2] raw: Fix mixed declarations error in raw_icmp_error().
https://git.kernel.org/netdev/net-next/c/5da39e31b1b0
- [v1,net-next,2/2] raw: Use helpers for the hlist_nulls variant.
https://git.kernel.org/netdev/net-next/c/f289c02bf41b
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:[~2022-06-20 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 23:29 [PATCH v1 net-next 0/2] raw: Fix nits of RCU conversion series Kuniyuki Iwashima
2022-06-19 23:29 ` [PATCH v1 net-next 1/2] raw: Fix mixed declarations error in raw_icmp_error() Kuniyuki Iwashima
2022-06-19 23:29 ` [PATCH v1 net-next 2/2] raw: Use helpers for the hlist_nulls variant Kuniyuki Iwashima
2022-06-20 8:20 ` 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=165571322792.28545.587082097048401953.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).