From: David Miller <davem@davemloft.net>
To: octavian.purdila@intel.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp: tcp_conn_request: fix build error when IPv6 is disabled
Date: Sun, 29 Jun 2014 23:47:19 -0700 (PDT) [thread overview]
Message-ID: <20140629.234719.906236334351806800.davem@davemloft.net> (raw)
In-Reply-To: <1403979654-7738-1-git-send-email-octavian.purdila@intel.com>
From: Octavian Purdila <octavian.purdila@intel.com>
Date: Sat, 28 Jun 2014 21:20:54 +0300
> Fixes build error introduced by commit 1fb6f159fd21c64 (tcp: add
> tcp_conn_request):
>
> net/ipv4/tcp_input.c: In function 'pr_drop_req':
> net/ipv4/tcp_input.c:5889:130: error: 'struct sock_common' has no member named 'skc_v6_daddr'
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Octavian Purdila <octavian.purdila@intel.com>
Applied, thanks.
prev parent reply other threads:[~2014-06-30 6:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 18:20 [PATCH net-next] tcp: tcp_conn_request: fix build error when IPv6 is disabled Octavian Purdila
2014-06-30 6:47 ` 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=20140629.234719.906236334351806800.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=octavian.purdila@intel.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).