From: Fabien Ribes <fribes@capgemini.fr>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: Networking: RFC1122 and 1123 status for kernel 2.4
Date: Wed, 13 Dec 2000 18:14:24 +0100 [thread overview]
Message-ID: <3A37AE70.B5F76D63@capgemini.fr> (raw)
In-Reply-To: <3A30F463.2EE04F4E@capgemini.fr> <200012081454.GAA02632@pizda.ninka.net> <20001208163154.A20038@gruyere.muc.suse.de> <200012081528.HAA02778@pizda.ninka.net> <20001208165855.A20706@gruyere.muc.suse.de> <200012112206.OAA00936@pizda.ninka.net>
"David S. Miller" a écrit :
>
> Date: Fri, 8 Dec 2000 16:58:55 +0100
> From: Andi Kleen <ak@suse.de>
>
> On Fri, Dec 08, 2000 at 07:28:15AM -0800, David S. Miller wrote:
> > I agree, I'll kill it unless you want to commit to this work
> > Andi. :-)
>
> Kill it ;)
>
> Done.
>
> Seriously, if someone wants to do this work please contact Andi
> or myself, we are willing to give some assistance.
I may get some time to work on this topic, but what do you mean by kill
it ? Is it the removal of RFC 1122 evaluation in modules' headers ? By
the way, is RFC 1122 still accurate ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-13 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 14:46 Networking: RFC1122 and 1123 status for kernel 2.4 Fabien Ribes
2000-12-08 14:54 ` David S. Miller
2000-12-08 15:31 ` Andi Kleen
2000-12-08 15:28 ` David S. Miller
2000-12-08 15:58 ` Andi Kleen
2000-12-08 16:41 ` kuznet
2000-12-08 16:48 ` Andi Kleen
2000-12-08 17:14 ` Alan Cox
2000-12-08 17:13 ` Alan Cox
2000-12-08 19:06 ` kuznet
2000-12-08 19:34 ` Christoph Hellwig
2000-12-08 23:17 ` Christoph Hellwig
2000-12-09 0:00 ` Alan Cox
2000-12-11 22:06 ` David S. Miller
2000-12-13 17:14 ` Fabien Ribes [this message]
2000-12-13 17:01 ` David S. Miller
2000-12-08 16:19 ` Fabien Ribes
2000-12-08 16:37 ` Andi Kleen
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=3A37AE70.B5F76D63@capgemini.fr \
--to=fribes@capgemini.fr \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.