netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: ishaangandhi <ishaangandhi@gmail.com>, davem@davemloft.net
Cc: kbuild-all@lists.01.org, ishaangandhi@gmail.com,
	netdev@vger.kernel.org, willemb@google.com
Subject: [RFC PATCH] icmp: icmp_identify_arrival_interface() can be static
Date: Fri, 12 Mar 2021 11:10:55 +0800	[thread overview]
Message-ID: <20210312031055.GA56313@2b632431e2d5> (raw)
In-Reply-To: <20210312004706.33046-1-ishaangandhi@gmail.com>


Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
 icmp.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/net/ipv4/icmp.c b/net/ipv4/icmp.c
index 8b63f2853e7b9..8cd003f5c8f59 100644
--- a/net/ipv4/icmp.c
+++ b/net/ipv4/icmp.c
@@ -586,8 +586,8 @@ static struct rtable *icmp_route_lookup(struct net *net,
  *  - ICMPv4 Parameter Problem
  */
 
-void icmp_identify_arrival_interface(struct sk_buff *skb, struct net *net, int room,
-				     struct icmphdr *icmph)
+static void icmp_identify_arrival_interface(struct sk_buff *skb, struct net *net, int room,
+					    struct icmphdr *icmph)
 {
 	unsigned int ext_len, if_index, orig_len, offset, extra_space_needed,
 		     word_aligned_orig_len, mtu, name_len, name_subobj_len;

  parent reply	other threads:[~2021-03-12  3:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12  0:47 [PATCH] icmp: support rfc 5837 ishaangandhi
2021-03-12  2:14 ` kernel test robot
2021-03-12  2:28 ` kernel test robot
2021-03-12  2:47 ` Willem de Bruijn
2021-03-12  3:10 ` kernel test robot
2021-03-12  3:10 ` kernel test robot [this message]
2021-03-15  8:29 ` [icmp] 42e5e7501e: BUG:KASAN:slab-out-of-bounds_in_pskb_expand_head kernel test robot

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=20210312031055.GA56313@2b632431e2d5 \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=ishaangandhi@gmail.com \
    --cc=kbuild-all@lists.01.org \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.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).