public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: jgarzik@mandrakesoft.com
Cc: alan@lxorguk.ukuu.org.uk, akpm@zip.com.au,
	aferber@techfak.uni-bielefeld.de, greearb@candelatech.com,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: Various 802.1Q VLAN driver patches. [try2]
Date: Fri, 01 Mar 2002 13:10:04 -0800 (PST)	[thread overview]
Message-ID: <20020301.131004.37152108.davem@redhat.com> (raw)
In-Reply-To: <3C7FEA55.2EFFA878@mandrakesoft.com>
In-Reply-To: <E16gu8n-000515-00@the-village.bc.nu> <3C7FEA55.2EFFA878@mandrakesoft.com>

   From: Jeff Garzik <jgarzik@mandrakesoft.com>
   Date: Fri, 01 Mar 2002 15:53:41 -0500
   
   Anyway, using CONFIG_xxx_MODULE has the problem I describe above.

It actually gets used for all the wrong reasons.

For example, in 2.4.x it is used to keep struct sock from bloating up
in include/net/sock.h unless you have all the protocols enabled.

Whereas with Arnaldo's changes in 2.5.x to split all the non-generic
junk out from struct sock, *_MODULE testing is no longer is needed for
that purpose.

Every existing reference I see in my 2.5.x tree for the networking is
"Duh, delete the ifdef".

  reply	other threads:[~2002-03-01 21:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 15:28 [BETA-0.93] Fourth test release of Tigon3 driver David S. Miller
2002-03-01 16:11 ` Various 802.1Q VLAN driver patches Ben Greear
2002-03-01 16:11   ` David S. Miller
2002-03-01 16:27     ` Various 802.1Q VLAN driver patches. [try2] Ben Greear
2002-03-01 16:30       ` Matti Aarnio
2002-03-01 16:33         ` Randy.Dunlap
2002-03-01 16:42           ` Jeff Garzik
2002-03-01 17:14         ` Various 802.1Q VLAN driver patches. [try3] Ben Greear
2002-03-01 19:24           ` Jeff Garzik
2002-03-01 16:35       ` Various 802.1Q VLAN driver patches. [try2] Jeff Garzik
2002-03-01 16:46         ` Andreas Ferber
2002-03-01 18:45           ` Andrew Morton
2002-03-01 18:50             ` David S. Miller
2002-03-01 19:02               ` Jeff Garzik
2002-03-01 21:00                 ` Alan Cox
2002-03-01 20:53                   ` Jeff Garzik
2002-03-01 21:10                     ` David S. Miller [this message]
2002-03-01 19:09           ` Jeff Garzik
2002-03-01 20:34             ` Andreas Ferber
2002-03-01 20:51               ` Jeff Garzik
2002-03-01 21:19                 ` Ben Greear
2002-03-01 21:19                   ` David S. Miller
2002-03-01 21:51                 ` Andreas Ferber
2002-03-01 16:40       ` David S. Miller
2002-03-01 19:17   ` Various 802.1Q VLAN driver patches Jeff Garzik
2002-03-01 19:44     ` Patrick Schaaf
2002-03-01 19:43       ` Jeff Garzik
2002-03-03 20:16         ` Teodor Iacob
2002-03-01 20:27       ` Donald Becker

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=20020301.131004.37152108.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=aferber@techfak.uni-bielefeld.de \
    --cc=akpm@zip.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greearb@candelatech.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox