From: "David S. Miller" <davem@redhat.com>
To: hvr@kernel.org
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] inet_ecn.h [2.4.16/2.5.0]
Date: Sun, 02 Dec 2001 16:09:31 -0800 (PST) [thread overview]
Message-ID: <20011202.160931.43504367.davem@redhat.com> (raw)
In-Reply-To: <1007295809.1531.4.camel@janus.txd.hvrlab.org>
In-Reply-To: <1007295809.1531.4.camel@janus.txd.hvrlab.org>
From: Herbert Valerio Riedel <hvr@kernel.org>
Date: 02 Dec 2001 13:23:29 +0100
...the following allows to build a kernel without CONFIG_INET...
That's not the correct fix, the correct one has been sent
to Marcelo. The net/core/*.c files are a little over agressive
in including TCP/IP headers when they shouldn't.
prev parent reply other threads:[~2001-12-03 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 12:23 [PATCH] inet_ecn.h [2.4.16/2.5.0] Herbert Valerio Riedel
2001-12-03 0:09 ` David S. Miller [this message]
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=20011202.160931.43504367.davem@redhat.com \
--to=davem@redhat.com \
--cc=hvr@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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