netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com,
	kuznet@ms2.inr.ac.ru, jmorris@intercode.com.au
Subject: 2.4.x IPSEC backport available
Date: Sun, 11 May 2003 14:46:21 -0700 (PDT)	[thread overview]
Message-ID: <20030511.144621.35018826.davem@redhat.com> (raw)


There is a 2.4.x backport of IPSEC available.  However there is a
STRONG caveat about using these changes in that we absolutely refuse
to take bug reports against this release, 2.5.x is where the active
development is taking place and thus where the testing is supposed to
take place.

This patch is a convenience for people, and nothing more.

Fetch it from:

	ftp://ftp.kernel.org/pub/linux/kernel/davem/IPSEC/linux-2.4.21-ipsec.patch
	bk://kernel.bkbits.net/davem/ipsec-2.4/

Enjoy.

                 reply	other threads:[~2003-05-11 21:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030511.144621.35018826.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=jmorris@intercode.com.au \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.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).