From: kernel test robot <lkp@intel.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org, davem@davemloft.net,
Willem de Bruijn <willemb@google.com>
Subject: [RFC PATCH] icmp6: ipv6_icmp_error_rfc4884() can be static
Date: Fri, 24 Jul 2020 12:33:08 +0800 [thread overview]
Message-ID: <20200724043308.GA2668@a9ba65664c75> (raw)
In-Reply-To: <20200723143357.451069-4-willemdebruijn.kernel@gmail.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
datagram.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/ipv6/datagram.c b/net/ipv6/datagram.c
index dd1d71e12b61a5..cc8ad7ddecdaa3 100644
--- a/net/ipv6/datagram.c
+++ b/net/ipv6/datagram.c
@@ -285,8 +285,8 @@ int ip6_datagram_connect_v6_only(struct sock *sk, struct sockaddr *uaddr,
}
EXPORT_SYMBOL_GPL(ip6_datagram_connect_v6_only);
-void ipv6_icmp_error_rfc4884(const struct sk_buff *skb,
- struct sock_ee_data_rfc4884 *out)
+static void ipv6_icmp_error_rfc4884(const struct sk_buff *skb,
+ struct sock_ee_data_rfc4884 *out)
{
switch (icmp6_hdr(skb)->icmp6_type) {
case ICMPV6_TIME_EXCEED:
prev parent reply other threads:[~2020-07-24 4:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 14:33 [PATCH net-next 0/3] icmp6: support rfc 4884 Willem de Bruijn
2020-07-23 14:33 ` [PATCH net-next 1/3] icmp: revise rfc4884 tests Willem de Bruijn
2020-07-23 14:33 ` [PATCH net-next 2/3] icmp: prepare rfc 4884 for ipv6 Willem de Bruijn
2020-07-23 14:33 ` [PATCH net-next 3/3] icmp6: support rfc 4884 Willem de Bruijn
2020-07-23 16:44 ` Jakub Kicinski
2020-07-23 17:13 ` Willem de Bruijn
2020-07-24 2:25 ` kernel test robot
2020-07-24 4:33 ` kernel test robot
2020-07-24 4:33 ` kernel test robot [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=20200724043308.GA2668@a9ba65664c75 \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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