All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: rene.herman@keyaccess.nl, 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 16:48:14 -0700	[thread overview]
Message-ID: <20080811164814.db41c20b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080809215020.1bb602e7@lxorguk.ukuu.org.uk>

On Sat, 9 Aug 2008 21:50:20 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Sat, 09 Aug 2008 19:39:53 +0200
> Rene Herman <rene.herman@keyaccess.nl> wrote:
> 
> > Grabbing ISA bus resources without anything or anyone telling us we
> > should can break boot on randconfig/allyesconfig builds by keeping
> > resources that are in fact owned by different hardware busy and does
> > as reported by Ingo Molnar.
> 
> Not an interesting case, and also wrong in the modular case where loading
> the module is a direct user action indicating clear intent to use the
> functionality *as is*.
> 
> NAK this one too.
> 
> At the very least make the requirement to say "like please run for real"
> dependant on it not being built modular - which is what was done for the
> last ones that were twiddled to keep Ingo amused.
> 

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.


  reply	other threads:[~2008-08-11 23:49 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 [this message]
2008-08-12  5:02     ` Rene Herman
2008-08-12  5:30       ` Andrew Morton
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=20080811164814.db41c20b.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 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.