netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hongbo Li <lihongbo22@huawei.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, jmaloy@redhat.com,
	ying.xue@windriver.com, pablo@netfilter.org,
	kadlec@netfilter.org, horms@kernel.org, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] make use of the helper macro LIST_HEAD()
Date: Sat, 07 Sep 2024 01:20:28 +0000	[thread overview]
Message-ID: <172567202850.2574896.10941650330610310039.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240904093243.3345012-1-lihongbo22@huawei.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 4 Sep 2024 17:32:38 +0800 you wrote:
> The macro LIST_HEAD() declares a list variable and
> initializes it, which can be used to simplify the steps
> of list initialization, thereby simplifying the code.
> These serials just do some equivalatent substitutions,
> and with no functional modifications.
> 
> Changes in v2:
>   - Keep the reverse xmas tree order as Simon's and
>     Pablo's suggested.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/5] net/ipv4: make use of the helper macro LIST_HEAD()
    https://git.kernel.org/netdev/net-next/c/cecbe5c8c803
  - [net-next,v2,2/5] net/tipc: make use of the helper macro LIST_HEAD()
    https://git.kernel.org/netdev/net-next/c/e636ba1a15e7
  - [net-next,v2,3/5] net/netfilter: make use of the helper macro LIST_HEAD()
    https://git.kernel.org/netdev/net-next/c/8b51455bbd45
  - [net-next,v2,4/5] net/ipv6: make use of the helper macro LIST_HEAD()
    https://git.kernel.org/netdev/net-next/c/2a7dd251b6fe
  - [net-next,v2,5/5] net/core: make use of the helper macro LIST_HEAD()
    https://git.kernel.org/netdev/net-next/c/17f01391903d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-09-07  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-04  9:32 [PATCH net-next v2 0/5] make use of the helper macro LIST_HEAD() Hongbo Li
2024-09-04  9:32 ` [PATCH net-next v2 1/5] net/ipv4: " Hongbo Li
2024-09-04  9:32 ` [PATCH net-next v2 2/5] net/tipc: " Hongbo Li
2024-09-04  9:32 ` [PATCH net-next v2 3/5] net/netfilter: " Hongbo Li
2024-09-04 10:03   ` Pablo Neira Ayuso
2024-09-04  9:32 ` [PATCH net-next v2 4/5] net/ipv6: " Hongbo Li
2024-09-04  9:32 ` [PATCH net-next v2 5/5] net/core: " Hongbo Li
2024-09-07  1: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=172567202850.2574896.10941650330610310039.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kadlec@netfilter.org \
    --cc=kuba@kernel.org \
    --cc=lihongbo22@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.org \
    --cc=ying.xue@windriver.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).