From: Steffen Klassert <steffen.klassert@secunet.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
Herbert Xu <herbert@gondor.hengli.com.au>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: linux-next: New trees - ipsec and ipsec-next
Date: Thu, 24 Jan 2013 07:13:15 +0100 [thread overview]
Message-ID: <20130124061315.GI9147@secunet.com> (raw)
Hello Stephen,
could you please add the ipsec and ipsec-next tree to linux-next?
The ipsec tree is intended to cover fixes for the ipsec networking
subsystem and the ipsec-next tree to cover changes for ipsec with
linux-next as target.
The trees are located at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git master
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
The ipsec tree follows David Miller's net tree, the ipsec-next tree follows
the net-next tree. So they should be merged after net and net-next.
Both trees were pulled recently, so they are currently empty.
Thanks!
next reply other threads:[~2013-01-24 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 6:13 Steffen Klassert [this message]
2013-01-24 23:20 ` linux-next: New trees - ipsec and ipsec-next Stephen Rothwell
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=20130124061315.GI9147@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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