From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Yue Haibing <yuehaibing@huawei.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, kuniyu@amazon.com
Cc: netdev@vger.kernel.org, yuehaibing@huawei.com
Subject: RE: [PATCH net-next] udp/udplite: Remove unused function declarations udp{,lite}_get_port()
Date: Sat, 05 Aug 2023 14:35:42 -0400 [thread overview]
Message-ID: <64ce967e6614f_3044329490@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20230805110009.44560-1-yuehaibing@huawei.com>
Yue Haibing wrote:
> Commit 6ba5a3c52da0 ("[UDP]: Make full use of proto.h.udp_hash innovation.")
> removed these implementations but leave declarations.
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
next prev parent reply other threads:[~2023-08-05 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 11:00 [PATCH net-next] udp/udplite: Remove unused function declarations udp{,lite}_get_port() Yue Haibing
2023-08-05 18:35 ` Willem de Bruijn [this message]
2023-08-07 8:00 ` patchwork-bot+netdevbpf
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=64ce967e6614f_3044329490@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuehaibing@huawei.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).