From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Lebrun Subject: Re: [net-next] ipv6: sr: export some functions of seg6local Date: Tue, 2 Jan 2018 20:11:48 +0000 Message-ID: <744656e9-b277-2915-e575-aea8b2c083be@gmail.com> References: <1514581784-1527-1-git-send-email-amsalam20@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: david.lebrun@uclouvain.be, netdev@vger.kernel.org To: Ahmed Abdelsalam , davem@davemloft.net, kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org Return-path: Received: from mail-wm0-f48.google.com ([74.125.82.48]:37192 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750749AbeABULU (ORCPT ); Tue, 2 Jan 2018 15:11:20 -0500 Received: by mail-wm0-f48.google.com with SMTP id f140so62574749wmd.2 for ; Tue, 02 Jan 2018 12:11:19 -0800 (PST) In-Reply-To: <1514581784-1527-1-git-send-email-amsalam20@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: On 12/29/2017 09:09 PM, Ahmed Abdelsalam wrote: > Some functions of seg6local are very useful to process SRv6 > encapsulated packets. > > This patch exports some functions of seg6local that are useful and > can be re-used at different parts of the kernel. > > The set of exported functions are: > (1) get_srh() > (2) advance_nextseg() > (3) lookup_nexthop If you want to export those functions, it's better to prefix them with e.g. seg6_: seg6_get_srh() seg6_advance_nextseg() seg6_lookup_nexthop() David