From: Dave Jones <davej@redhat.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: another attempt to kill off linux/config.h
Date: Wed, 4 Oct 2006 14:01:22 -0400 [thread overview]
Message-ID: <20061004180122.GC13079@redhat.com> (raw)
In-Reply-To: <1159962332.3000.15.camel@laptopd505.fenrus.org>
On Wed, Oct 04, 2006 at 01:45:32PM +0200, Arjan van de Ven wrote:
> > Removing it for real will be a pain for external modules.
> > They could of course detect that it is missing and then
> > drop it.
> > I would suggest to keep the #warning in 2.6.19 and only
> > remove it for real for 2.6.20.
>
> they'll have to change anyway; delaying it one release doesn't actually
> change that. And you can bet on most modules ignoring the warning anyway
> and wait until the thing really is gone... making the value that this
> extra delay has basically zero. While the cost is that more false users
> will sneak into the kernel ;(
My thoughts exactly. Since when did we give a damn about keeping
external modules compiling anyway?
> Maybe Fedora can ship with an #error here early on; an #error at least
> can provide a helpful message on how to fix it.
The #warn has been there for a few weeks in the fc6pre kernels, but it's
easily changed.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-10-04 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 7:44 another attempt to kill off linux/config.h Dave Jones
2006-10-04 11:24 ` Sam Ravnborg
2006-10-04 11:45 ` Arjan van de Ven
2006-10-04 18:01 ` Dave Jones [this message]
2006-10-04 18:26 ` Sam Ravnborg
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=20061004180122.GC13079@redhat.com \
--to=davej@redhat.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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.