From: Steffen Klassert <steffen.klassert@secunet.com>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Wei Yongjun <weiyongjun1@huawei.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] xfrm: Make function xfrm_dev_register static
Date: Fri, 19 May 2017 13:15:23 +0200 [thread overview]
Message-ID: <20170519111522.GG22049@secunet.com> (raw)
In-Reply-To: <20170518155138.19962-1-weiyj.lk@gmail.com>
On Thu, May 18, 2017 at 03:51:38PM +0000, Wei Yongjun wrote:
> From: Wei Yongjun <weiyongjun1@huawei.com>
>
> Fixes the following sparse warning:
>
> net/xfrm/xfrm_device.c:141:5: warning:
> symbol 'xfrm_dev_register' was not declared. Should it be static?
>
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
Applied to ipsec-next, thanks!
prev parent reply other threads:[~2017-05-19 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 15:51 [PATCH net-next] xfrm: Make function xfrm_dev_register static Wei Yongjun
2017-05-19 11:15 ` Steffen Klassert [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=20170519111522.GG22049@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=weiyj.lk@gmail.com \
--cc=weiyongjun1@huawei.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).