From: Risto Suominen <risto.suominen@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: jgarzik@pobox.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org,
Grant Grundler <grundler@parisc-linux.org>
Subject: Re: [PATCH 002/002] de2104x: support for systems lacking cache coherence
Date: Tue, 10 Feb 2009 09:16:06 +0200 [thread overview]
Message-ID: <46e1c7760902092316g432a432dy10398030a5838ba9@mail.gmail.com> (raw)
In-Reply-To: <20090209170120.85e192be.akpm@linux-foundation.org>
2009/2/10 Andrew Morton <akpm@linux-foundation.org>:
>
> Please prefer to prepare patches in `patch -p1' form:
>
> --- a/drivers/net/tulip/Kconfig
> +++ a/drivers/net/tulip/Kconfig
>
I'll try to remember that.
> I think CONFIG_DE2104X_DSL is always defined if this driver is being
> compiled. So the Kconfig `default' should suffice here? In which case
> we can do
>
> #define DSL CONFIG_DE2104X_DSL
>
> and leave it at that.
>
> In which case we can do away with DSL everywhere and just use
> CONFIG_DE2104X_DSL here.
>
I was thinking of the case where someone just compiles without reconfiguring.
> But really, we shouldn't do this at configuration time at all. It
> would be much better to do it at runtime, via a module parameter.
>
Well, yeah, but that would probably cost cpu cycles. At least it would
mean lots of changes.
> And it would be much^2 better to do it automatically, based upon the
> chip probing information or whatever. That's probably hard.
>
I agree.
> Can remove the ifdefs here. A zero-length array is OK, and will
> consume zero space.
>
I was uncertain whether this applies to all compilers. I kind of
remember opposite cases in the past.
Risto
prev parent reply other threads:[~2009-02-10 7:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46e1c7760902071330i5362fe4fvd99fc7075fc666d3@mail.gmail.com>
2009-02-09 7:27 ` Fwd: [PATCH 002/002] de2104x: support for systems lacking cache coherence Risto Suominen
2009-02-09 7:45 ` David Miller
2009-02-09 8:22 ` Risto Suominen
2009-02-09 8:29 ` David Miller
2009-02-09 8:35 ` Risto Suominen
2009-02-09 16:58 ` Krzysztof Halasa
2009-02-09 19:22 ` Risto Suominen
2009-02-09 22:51 ` David Miller
2009-02-10 1:45 ` Krzysztof Halasa
2009-02-10 1:50 ` David Miller
2009-02-10 23:21 ` David Miller
2009-02-11 12:18 ` Risto Suominen
2009-02-11 12:31 ` Risto Suominen
2009-02-11 21:39 ` David Miller
2009-02-13 3:42 ` Benjamin Herrenschmidt
2009-02-10 1:01 ` Andrew Morton
2009-02-10 1:07 ` David Miller
2009-02-10 7:16 ` Risto Suominen [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=46e1c7760902092316g432a432dy10398030a5838ba9@mail.gmail.com \
--to=risto.suominen@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=grundler@parisc-linux.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).