Patchwork IPSEC maintainership...

login
register
mail settings
Submitter David Miller
Date Oct. 15, 2012, 5:38 p.m.
Message ID <20121015.133833.2211899390966002142.davem@davemloft.net>
Download mbox | patch
Permalink /patch/191613/
State Accepted
Delegated to: David Miller
Headers show

Comments

David Miller - Oct. 15, 2012, 5:38 p.m.
Steffen, after some discussions with Herbert we'd like to formally
recognize your outstanding contributions to the IPSEC stack over
the past few years by listing you explicitly as a maintainer as
per the patch below.

Let us know if you are OK with this.

Thanks!

--------------------
MAINTAINERS: Add explicit section for IPSEC networking.

Signed-off-by: David S. Miller <davem@davemloft.net>

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Steffen Klassert - Oct. 16, 2012, 6:11 a.m.
On Mon, Oct 15, 2012 at 01:38:33PM -0400, David Miller wrote:
> 
> Steffen, after some discussions with Herbert we'd like to formally
> recognize your outstanding contributions to the IPSEC stack over
> the past few years by listing you explicitly as a maintainer as
> per the patch below.
> 
> Let us know if you are OK with this.

I'm absolutely OK with this, of course :)

Being one of the maintainers, I'd like to run our automated IPsec
tests on incomming paches before they get applied. So I'd think
about a workflow and propose something if you are OK with that.

> 
> Thanks!
> 
> --------------------
> MAINTAINERS: Add explicit section for IPSEC networking.
> 
> Signed-off-by: David S. Miller <davem@davemloft.net>

Acked-by: Steffen Klassert <steffen.klassert@secunet.com>

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
David Miller - Oct. 16, 2012, 6:14 a.m.
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Tue, 16 Oct 2012 08:11:54 +0200

> On Mon, Oct 15, 2012 at 01:38:33PM -0400, David Miller wrote:
>> 
>> Steffen, after some discussions with Herbert we'd like to formally
>> recognize your outstanding contributions to the IPSEC stack over
>> the past few years by listing you explicitly as a maintainer as
>> per the patch below.
>> 
>> Let us know if you are OK with this.
> 
> I'm absolutely OK with this, of course :)
> 
> Being one of the maintainers, I'd like to run our automated IPsec
> tests on incomming paches before they get applied. So I'd think
> about a workflow and propose something if you are OK with that.

If you want you can maintainer an IPSEC GIT tree, where you apply any
submitted IPSEC changes.

Once you are satisfied with their quality and they pass your tests,
you simply send me a formal GIT pull request just like any other
networking subsystem (netfilter, wireless, etc.) currently does.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Steffen Klassert - Oct. 16, 2012, 6:21 a.m.
On Tue, Oct 16, 2012 at 02:14:35AM -0400, David Miller wrote:
> 
> If you want you can maintainer an IPSEC GIT tree, where you apply any
> submitted IPSEC changes.
> 
> Once you are satisfied with their quality and they pass your tests,
> you simply send me a formal GIT pull request just like any other
> networking subsystem (netfilter, wireless, etc.) currently does.

Sounds good, let's do it this way. I'll set up a git tree and
process the incomming IPsec patches.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Steffen Klassert - Oct. 17, 2012, 9:13 a.m.
On Tue, Oct 16, 2012 at 02:14:35AM -0400, David Miller wrote:
> 
> If you want you can maintainer an IPSEC GIT tree, where you apply any
> submitted IPSEC changes.

I've set up two git tries at kernel.org, an 'ipsec' tree that tracks the
net tree and an 'ipsec-next' tree that tracks the net-next tree.

They are located at

git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git

Once the workflow for IPsec patches is established, I'll ask for
linux-next inclusion of the ipsec-next tree to get early stage
testing of the IPsec changes.

Regarding my own IPsec patches, I'll continue to send them to netdev
for review with the remark that I'll apply them to the appropriate
tree if nobody has objections.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index e73060f..6d6632f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5019,6 +5019,20 @@  F:	net/ipv6/
 F:	include/net/ip*
 F:	arch/x86/net/*
 
+NETWORKING [IPSEC]
+M:	Steffen Klassert <steffen.klassert@secunet.com>
+M:	Herbert Xu <herbert@gondor.apana.org.au>
+M:	"David S. Miller" <davem@davemloft.net>
+L:	netdev@vger.kernel.org
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
+S:	Maintained
+F:	net/xfrm/
+F:	net/key/
+F:	net/ipv4/xfrm*
+F:	net/ipv6/xfrm*
+F:	include/uapi/linux/xfrm.h
+F:	include/net/xfrm.h
+
 NETWORKING [LABELED] (NetLabel, CIPSO, Labeled IPsec, SECMARK)
 M:	Paul Moore <paul@paul-moore.com>
 L:	netdev@vger.kernel.org