* IPSEC maintainership...
@ 2012-10-15 17:38 David Miller
2012-10-16 6:11 ` Steffen Klassert
0 siblings, 1 reply; 5+ messages in thread
From: David Miller @ 2012-10-15 17:38 UTC (permalink / raw)
To: steffen.klassert; +Cc: netdev, herbert
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>
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
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: IPSEC maintainership...
2012-10-15 17:38 IPSEC maintainership David Miller
@ 2012-10-16 6:11 ` Steffen Klassert
2012-10-16 6:14 ` David Miller
0 siblings, 1 reply; 5+ messages in thread
From: Steffen Klassert @ 2012-10-16 6:11 UTC (permalink / raw)
To: David Miller; +Cc: netdev, herbert
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>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: IPSEC maintainership...
2012-10-16 6:11 ` Steffen Klassert
@ 2012-10-16 6:14 ` David Miller
2012-10-16 6:21 ` Steffen Klassert
2012-10-17 9:13 ` Steffen Klassert
0 siblings, 2 replies; 5+ messages in thread
From: David Miller @ 2012-10-16 6:14 UTC (permalink / raw)
To: steffen.klassert; +Cc: netdev, herbert
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: IPSEC maintainership...
2012-10-16 6:14 ` David Miller
@ 2012-10-16 6:21 ` Steffen Klassert
2012-10-17 9:13 ` Steffen Klassert
1 sibling, 0 replies; 5+ messages in thread
From: Steffen Klassert @ 2012-10-16 6:21 UTC (permalink / raw)
To: David Miller; +Cc: netdev, herbert
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: IPSEC maintainership...
2012-10-16 6:14 ` David Miller
2012-10-16 6:21 ` Steffen Klassert
@ 2012-10-17 9:13 ` Steffen Klassert
1 sibling, 0 replies; 5+ messages in thread
From: Steffen Klassert @ 2012-10-17 9:13 UTC (permalink / raw)
To: David Miller; +Cc: netdev, herbert
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-10-17 9:13 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-10-15 17:38 IPSEC maintainership David Miller
2012-10-16 6:11 ` Steffen Klassert
2012-10-16 6:14 ` David Miller
2012-10-16 6:21 ` Steffen Klassert
2012-10-17 9:13 ` Steffen Klassert
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).