All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
	davem@davemloft.net, kuba@kernel.org, marcelo.leitner@gmail.com
Subject: Re: [PATCH net-next] sctp: move hlist_node and hashent out of sctp_ep_common
Date: Thu, 23 Dec 2021 11:20:09 +0000	[thread overview]
Message-ID: <164025840975.28761.7027815149215841178.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <21619581e3ed03aa08156f280b3181b9c2823600.1640122830.git.lucien.xin@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue, 21 Dec 2021 16:40:30 -0500 you wrote:
> Struct sctp_ep_common is included in both asoc and ep, but hlist_node
> and hashent are only needed by ep after asoc_hashtable was dropped by
> Commit b5eff7128366 ("sctp: drop the old assoc hashtable of sctp").
> 
> So it is better to move hlist_node and hashent from sctp_ep_common to
> sctp_endpoint, and it saves some space for each asoc.
> 
> [...]

Here is the summary with links:
  - [net-next] sctp: move hlist_node and hashent out of sctp_ep_common
    https://git.kernel.org/netdev/net-next/c/3d3b2f57d444

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



      reply	other threads:[~2021-12-23 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 21:40 [PATCH net-next] sctp: move hlist_node and hashent out of sctp_ep_common Xin Long
2021-12-23 11: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=164025840975.28761.7027815149215841178.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.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.