public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: scole@lanl.gov
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CONFIG_EISA note in Documentation/Configure.help
Date: Tue, 14 Nov 2000 16:06:47 -0500	[thread overview]
Message-ID: <3A11A967.A2EA6D20@mandrakesoft.com> (raw)
In-Reply-To: <00111413485901.03227@spc.esa.lanl.gov>

Steven Cole wrote:
> Well, the CONFIG_EISA option is there.  My little patch was just intended to
> slightly enlighten those prone to "lets see what this option does".  I
> compiled test11-pre4 both with and without CONFIG_EISA and the difference is
> very slight.  Of course, if you had more items with EISA code, this difference
> would be bigger.
> 
>  848 -rw-r--r--    1 root     root       868179 Nov 14 13:32 bzImage
>  848 -rw-r--r--    1 root     root       867973 Nov 14 13:28 bzImage.no_eisa
> 
> The difference probably comes from my 3c59x driver.
> 
> I also uglied up the 3c59x.c code with #ifdef CONFIG_EISA around the
> six sections relavant to EISA to see if that would save anything, and the
> object file was only 318 bytes smaller, probably not worth the uglyness of
> the six ifdefs.  That modified code was not used in the above comparison.

When !CONFIG_EISA, the global variable 'EISA_bus' is unconditionally
zero.  Therefore you merely need to test EISA_bus, as existing code
already should be doing..  As for 3c59x patches, they should go to the
maintainer, Andrew Morton..

	Jeff


-- 
Jeff Garzik             |
Building 1024           | The chief enemy of creativity is "good" sense
MandrakeSoft            |          -- Picasso
-
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/

  reply	other threads:[~2000-11-14 21:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-14 20:48 [PATCH] CONFIG_EISA note in Documentation/Configure.help Steven Cole
2000-11-14 21:06 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-17 23:47 Andries.Brouwer
2000-11-14 23:37 Andrzej Krzysztofowicz
2000-11-14 21:22 Steven Cole
2000-11-14  0:07 Steven Cole
2000-11-14 19:59 ` Andries Brouwer
2000-11-14 20:23   ` Jeff Garzik
2000-11-14 21:00     ` Andries Brouwer
     [not found]   ` <3A127070.7DEE2527@yahoo.com>
2000-11-17 22:01     ` Andries Brouwer
2000-11-17 23:24       ` Alan Cox
2000-11-18 11:26       ` Christer Weinigel

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=3A11A967.A2EA6D20@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scole@lanl.gov \
    /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