From: Sabrina Dubroca <sd@queasysnail.net>
To: Fan Du <fan.du@windriver.com>
Cc: steffen.klassert@secunet.com, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCHv2 net-next 1/4] flowcache: Namespacify flowcache global parameters with xfrm
Date: Tue, 14 Jan 2014 19:53:29 +0100 [thread overview]
Message-ID: <20140114185329.GA1971@kria> (raw)
In-Reply-To: <1389663588-29678-2-git-send-email-fan.du@windriver.com>
2014-01-14, 09:39:44 +0800, Fan Du wrote:
> Since flowcache is tightly coupled with IPsec, so it would be
> easier to put flow cache global parameters here into xfrm
> namespace part.
>
> Signed-off-by: Fan Du <fan.du@windriver.com>
> ---
> include/net/netns/xfrm.h | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/include/net/netns/xfrm.h b/include/net/netns/xfrm.h
> index 1006a26..52d0086 100644
> --- a/include/net/netns/xfrm.h
> +++ b/include/net/netns/xfrm.h
> @@ -6,6 +6,7 @@
> #include <linux/workqueue.h>
> #include <linux/xfrm.h>
> #include <net/dst_ops.h>
> +#include <net/flowcache.h>
You are including a file that doesn't exist yet. You create it later,
with patch 2. This breaks bisection.
--
Sabrina
next prev parent reply other threads:[~2014-01-14 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 1:39 [PATCHv2 net-next 0/4] Make flow cache name space aware Fan Du
2014-01-14 1:39 ` [PATCHv2 net-next 1/4] flowcache: Namespacify flowcache global parameters with xfrm Fan Du
2014-01-14 18:53 ` Sabrina Dubroca [this message]
2014-01-14 1:39 ` [PATCHv2 net-next 2/4] flowcache: Make flowcache entry inserting/flushing in per-net style Fan Du
2014-01-14 1:39 ` [PATCHv2 net-next 3/4] flowcache: Fixup flow cache part in xfrm policy Fan Du
2014-01-14 18:59 ` Sabrina Dubroca
2014-01-15 7:19 ` Fan Du
2014-01-14 1:39 ` [PATCHv2 net-next 4/4] flowcache: Bring net/core/flow.c under IPsec maintain scope Fan Du
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=20140114185329.GA1971@kria \
--to=sd@queasysnail.net \
--cc=davem@davemloft.net \
--cc=fan.du@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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