From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for May 16 (net/core)
Date: Tue, 16 May 2017 09:28:30 -0700 [thread overview]
Message-ID: <f63533e7-edd3-4c0d-ddff-e3409d15abc6@infradead.org> (raw)
In-Reply-To: <20170516112125.517607f8@canb.auug.org.au>
On 05/15/17 18:21, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20170515:
>
on i386 or x86_64:
when CONFIG_INET is not enabled:
../net/core/sock.c: In function 'skb_orphan_partial':
../net/core/sock.c:1810:2: error: implicit declaration of function 'skb_is_tcp_pure_ack' [-Werror=implicit-function-declaration]
if (skb_is_tcp_pure_ack(skb))
^
--
~Randy
next prev parent reply other threads:[~2017-05-16 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 1:21 linux-next: Tree for May 16 Stephen Rothwell
2017-05-16 16:28 ` Randy Dunlap [this message]
2017-05-16 19:44 ` linux-next: Tree for May 16 (net/core) Paul Gortmaker
2017-05-16 20:12 ` Eric Dumazet
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=f63533e7-edd3-4c0d-ddff-e3409d15abc6@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).