From: "David S. Miller" <davem@davemloft.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com
Subject: Re: [IPSEC] Stop using dst->xfrm
Date: Tue, 25 Jan 2005 22:23:01 -0800 [thread overview]
Message-ID: <20050125222301.5fb62202.davem@davemloft.net> (raw)
In-Reply-To: <20050121102319.GA3160@gondor.apana.org.au>
On Fri, 21 Jan 2005 21:23:19 +1100
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> Here is a precursor to the xfrm dst consolidation that I talked about.
> In order to be able to store multiple SAs in one dst, we need to stop
> using dst->xfrm directly.
>
> The following patch does that for the ->output() functions.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
I'm going to create a 2.6.12 pending queue and put this and
any forthcoming xfrm dst work there.
next prev parent reply other threads:[~2005-01-26 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 10:23 [IPSEC] Stop using dst->xfrm Herbert Xu
2005-01-22 5:58 ` David Dillow
2005-01-26 6:18 ` David S. Miller
2005-01-26 7:21 ` Herbert Xu
2005-01-26 10:21 ` Herbert Xu
2005-01-26 6:23 ` David S. Miller [this message]
2005-02-09 4:58 ` David S. Miller
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=20050125222301.5fb62202.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).