From: roopa <roopa@cumulusnetworks.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] lwtunnel: Make lwtun_encaps[] static
Date: Wed, 29 Jul 2015 12:35:27 -0700 [thread overview]
Message-ID: <55B92AFF.3080101@cumulusnetworks.com> (raw)
In-Reply-To: <66e6473d98879c465cf4965d44230374c716ed25.1438155918.git.tgraf@suug.ch>
On 7/29/15, 12:45 AM, Thomas Graf wrote:
> Any external user should use the registration API instead of
> accessing this directly.
>
> Cc: Roopa Prabhu <roopa@cumulusnetworks.com>
> Signed-off-by: Thomas Graf <tgraf@suug.ch>
Acked-by: Roopa Prabhu <roopa@cumulusnetworks.com>
thanks.
> ---
> include/net/lwtunnel.h | 3 ---
> net/core/lwtunnel.c | 2 +-
> 2 files changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/include/net/lwtunnel.h b/include/net/lwtunnel.h
> index b020390..33bd309 100644
> --- a/include/net/lwtunnel.h
> +++ b/include/net/lwtunnel.h
> @@ -31,9 +31,6 @@ struct lwtunnel_encap_ops {
> int (*cmp_encap)(struct lwtunnel_state *a, struct lwtunnel_state *b);
> };
>
> -extern const struct lwtunnel_encap_ops __rcu *
> - lwtun_encaps[LWTUNNEL_ENCAP_MAX+1];
> -
> #ifdef CONFIG_LWTUNNEL
> static inline struct lwtunnel_state *
> lwtstate_get(struct lwtunnel_state *lws)
> diff --git a/net/core/lwtunnel.c b/net/core/lwtunnel.c
> index 5f7fae7..c240c89 100644
> --- a/net/core/lwtunnel.c
> +++ b/net/core/lwtunnel.c
> @@ -37,7 +37,7 @@ struct lwtunnel_state *lwtunnel_state_alloc(int encap_len)
> }
> EXPORT_SYMBOL(lwtunnel_state_alloc);
>
> -const struct lwtunnel_encap_ops __rcu *
> +static const struct lwtunnel_encap_ops __rcu *
> lwtun_encaps[LWTUNNEL_ENCAP_MAX + 1] __read_mostly;
>
> int lwtunnel_encap_add_ops(const struct lwtunnel_encap_ops *ops,
next prev parent reply other threads:[~2015-07-29 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 7:45 [PATCH net-next] lwtunnel: Make lwtun_encaps[] static Thomas Graf
2015-07-29 19:35 ` roopa [this message]
2015-07-30 5:59 ` David Miller
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=55B92AFF.3080101@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.