netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] MAINTAINERS: Update the IPsec maintainer entry
Date: Tue, 17 Dec 2013 14:59:31 -0500 (EST)	[thread overview]
Message-ID: <20131217.145931.2281784823591689152.davem@davemloft.net> (raw)
In-Reply-To: <20131213115605.GP31491@secunet.com>

From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Fri, 13 Dec 2013 12:56:05 +0100

> Add the IPsec git trees and some pure IPsec modules
> to the IPsec section in the MAINTAINERS file.
> 
> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>

As a documentation fix, I've applied this to 'net', thanks.

      reply	other threads:[~2013-12-17 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 11:56 [PATCH net-next] MAINTAINERS: Update the IPsec maintainer entry Steffen Klassert
2013-12-17 19:59 ` 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=20131217.145931.2281784823591689152.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --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).