From: Andrew Morton <akpm@linux-foundation.org>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@linuxfoundation.org, fritz@isdn4linux.de, kkeil@suse.de,
isdn4linux@listserv.isdn4linux.de, linux-kernel@vger.kernel.org,
mingo@elte.hu
Subject: Re: [PATCH] ISDN: make ICN not auto-grab port 0x320
Date: Mon, 11 Aug 2008 22:30:43 -0700 [thread overview]
Message-ID: <20080811223043.9ad55c51.akpm@linux-foundation.org> (raw)
In-Reply-To: <48A11952.6090203@keyaccess.nl>
On Tue, 12 Aug 2008 07:02:10 +0200 Rene Herman <rene.herman@keyaccess.nl> wrote:
> On 12-08-08 01:48, Andrew Morton wrote:
>
> > otoh it's a bit sad to break allyesconfig kernels - there is
> > regression-testing value in being able to run such kernels.
> >
> > I wonder if we can add a new boot option `allyesconfig-test' or
> > something like that, and then, within the offending drivers, test that
> > flag and take suitable avoiding action.
> >
> > Or we could do it at compile-time - define
> > CONFIG_ALLYESCONFIG_TESTING in some fashion.
>
> Yes, latter I'd feel with the thing most against it that there aren't
> actually many that need it.
I think the boot option is the way, if at all.
Because the config option isn't very usable. What's to stop someone
from doing `make allyesconfig' and then menually editing the .config so
it's no longer truly an allyesconfig .config?
otoh, if is't purely a manual setting rather than some automagic thing
then it might be workable. CONFIG_INGO :)
next prev parent reply other threads:[~2008-08-12 5:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 17:39 [PATCH] ISDN: make ICN not auto-grab port 0x320 Rene Herman
2008-08-09 20:50 ` Alan Cox
2008-08-11 23:48 ` Andrew Morton
2008-08-12 5:02 ` Rene Herman
2008-08-12 5:30 ` Andrew Morton [this message]
2008-08-12 13:08 ` Adrian Bunk
2008-08-12 13:26 ` Rene Herman
2008-08-12 13:43 ` Adrian Bunk
2008-08-12 13:53 ` Rene Herman
2008-08-12 14:03 ` Adrian Bunk
2008-08-12 14:45 ` Rene Herman
2008-08-12 15:23 ` Adrian Bunk
2008-08-12 13:46 ` Rene Herman
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=20080811223043.9ad55c51.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akpm@linuxfoundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=fritz@isdn4linux.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rene.herman@keyaccess.nl \
/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