public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Reji Thomas <rejithomas@juniper.net>, kuba@kernel.org
Cc: kbuild-all@lists.01.org, david.lebrun@uclouvain.be,
	davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, rejithomas@juniper.net,
	rejithomas.d@gmail.com
Subject: [RFC PATCH] IPv6: sr: seg6_strict_lookup_nexthop() can be static
Date: Wed, 14 Oct 2020 00:11:53 +0800	[thread overview]
Message-ID: <20201013161153.GA54884@b456307fa776> (raw)
In-Reply-To: <20201013120151.9777-1-rejithomas@juniper.net>


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

diff --git a/net/ipv6/seg6_local.c b/net/ipv6/seg6_local.c
index 1a669f12d56c9d..e949d24036c2cd 100644
--- a/net/ipv6/seg6_local.c
+++ b/net/ipv6/seg6_local.c
@@ -219,8 +219,8 @@ int seg6_lookup_nexthop(struct sk_buff *skb,
 	return seg6_lookup_any_nexthop(skb, nhaddr, 0, tbl_id, false);
 }
 
-int seg6_strict_lookup_nexthop(struct sk_buff *skb,
-			       struct in6_addr *nhaddr, int oif, u32 tbl_id)
+static int seg6_strict_lookup_nexthop(struct sk_buff *skb,
+				      struct in6_addr *nhaddr, int oif, u32 tbl_id)
 {
 	return seg6_lookup_any_nexthop(skb, nhaddr, oif, tbl_id, false);
 }

  parent reply	other threads:[~2020-10-13 16:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 12:01 [PATCH] IPv6: sr: Fix End.X nexthop to use oif Reji Thomas
2020-10-13 16:11 ` kernel test robot
2020-10-13 16:11 ` kernel test robot [this message]
2020-10-13 17:01 ` Jakub Kicinski
2020-10-14 18:34 ` 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=20201013161153.GA54884@b456307fa776 \
    --to=lkp@intel.com \
    --cc=davem@davemloft.net \
    --cc=david.lebrun@uclouvain.be \
    --cc=kbuild-all@lists.01.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rejithomas.d@gmail.com \
    --cc=rejithomas@juniper.net \
    /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