From: "David S. Miller" <davem@redhat.com>
To: jgarzik@pobox.com
Cc: toml@us.ibm.com, linux-kernel@vger.kernel.org, kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] IPSec protocol application order
Date: Wed, 19 Feb 2003 13:20:48 -0800 (PST) [thread overview]
Message-ID: <20030219.132048.35036153.davem@redhat.com> (raw)
In-Reply-To: <20030219212950.GC4977@gtf.org>
From: Jeff Garzik <jgarzik@pobox.com>
Date: Wed, 19 Feb 2003 16:29:50 -0500
hmmm... do you really need to duplicate all that code, just to define
the order?
It's not even a kernel issue as Alexey and myself said in other
emails, the kernel merely does what the user application asks it to do
next prev parent reply other threads:[~2003-02-19 21:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 20:42 [PATCH] IPSec protocol application order Tom Lendacky
2003-02-19 21:29 ` Jeff Garzik
2003-02-19 21:20 ` David S. Miller [this message]
2003-02-19 22:05 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 21:48 Tom Lendacky
2003-02-19 21:39 ` David S. Miller
2003-02-19 22:07 ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-19 23:03 Tom Lendacky
2003-02-20 1:32 ` David S. Miller
2003-02-20 0:57 ` Chris Wedgwood
2003-02-20 6:51 ` David S. Miller
2003-02-20 14:40 Tom Lendacky
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=20030219.132048.35036153.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=toml@us.ibm.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