From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: fengguang.wu@intel.com, kbuild-all@01.org,
linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru,
jmorris@namei.org, yoshfuji@linux-ipv6.org, kaber@trash.net,
netdev@vger.kernel.org, colona@arista.com, gilligan@arista.com,
mowat@arista.com
Subject: Re: [RFC PATCH linus] tcp: md5: tcp_md5_do_lookup_exact() can be static
Date: Thu, 06 Jul 2017 10:55:38 +0100 (WEST) [thread overview]
Message-ID: <20170706.105538.1784895348831188824.davem@davemloft.net> (raw)
In-Reply-To: <20170706102712.3904c199@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 6 Jul 2017 10:27:12 +1000
> Hi,
>
> Not sure why you sent this to me ... it fixes a commit in the net-next
> tree (now in Linus' tree) ...
>
> On Thu, 6 Jul 2017 07:58:53 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
>>
>> Fixes: 0c5f0311f690 ("Add linux-next specific files for 20170705")
>
> Actually: Fixes: 6797318e623d ("tcp: md5: add an address prefix for key lookup")
Applied with correct fixes tag, thanks.
prev parent reply other threads:[~2017-07-06 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 23:58 net/ipv4/tcp_ipv4.c:950:23: sparse: symbol 'tcp_md5_do_lookup_exact' was not declared. Should it be static? kbuild test robot
2017-07-05 23:58 ` [RFC PATCH linus] tcp: md5: tcp_md5_do_lookup_exact() can be static kbuild test robot
2017-07-06 0:27 ` Stephen Rothwell
2017-07-06 8:57 ` Fengguang Wu
2017-07-06 9:55 ` David Miller [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=20170706.105538.1784895348831188824.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=colona@arista.com \
--cc=fengguang.wu@intel.com \
--cc=gilligan@arista.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kbuild-all@01.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mowat@arista.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yoshfuji@linux-ipv6.org \
/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).