From: David Ahern <dsahern@kernel.org>
To: Yue Haibing <yuehaibing@huawei.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] neighbour: Remove unused function declaration pneigh_for_each()
Date: Sun, 6 Aug 2023 19:07:31 -0600 [thread overview]
Message-ID: <ee919c2c-090f-2613-6545-d69e05f95e3f@kernel.org> (raw)
In-Reply-To: <20230805105033.45700-1-yuehaibing@huawei.com>
On 8/5/23 4:50 AM, Yue Haibing wrote:
> pneigh_for_each() is never implemented since the beginning of git history.
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
> ---
> include/net/neighbour.h | 2 --
> 1 file changed, 2 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2023-08-07 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 10:50 [PATCH net-next] neighbour: Remove unused function declaration pneigh_for_each() Yue Haibing
2023-08-07 1:07 ` David Ahern [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=ee919c2c-090f-2613-6545-d69e05f95e3f@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--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).