netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fan Du <fan.du@windriver.com>
To: <steffen.klassert@secunet.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: [PATCHv2 net-next 4/4] flowcache: Bring net/core/flow.c under IPsec maintain scope
Date: Tue, 14 Jan 2014 09:39:47 +0800	[thread overview]
Message-ID: <1389663588-29678-5-git-send-email-fan.du@windriver.com> (raw)
In-Reply-To: <1389663588-29678-1-git-send-email-fan.du@windriver.com>

As flow cache is mainly manipulated from IPsec.

Signed-off-by: Fan Du <fan.du@windriver.com>
---
 MAINTAINERS |    1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index e11d495..14ad385 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5916,6 +5916,7 @@ L:	netdev@vger.kernel.org
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git
 T:	git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git
 S:	Maintained
+F:	net/core/flow.c
 F:	net/xfrm/
 F:	net/key/
 F:	net/ipv4/xfrm*
-- 
1.7.9.5

      parent reply	other threads:[~2014-01-14  1:39 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
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 ` Fan Du [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=1389663588-29678-5-git-send-email-fan.du@windriver.com \
    --to=fan.du@windriver.com \
    --cc=davem@davemloft.net \
    --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;
as well as URLs for NNTP newsgroup(s).