public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	linux-kernel@vger.kernel.org, james.bottomley@steeleye.com
Subject: Re: [PATCH] init. mca_bus_type even if !MCA_bus
Date: Mon, 17 May 2004 15:58:16 -0700	[thread overview]
Message-ID: <20040517225816.GA21333@kroah.com> (raw)
In-Reply-To: <20040517155222.11f4b253.akpm@osdl.org>

On Mon, May 17, 2004 at 03:52:22PM -0700, Andrew Morton wrote:
> "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> >
> > On Mon, 17 May 2004 15:14:12 -0700 Andrew Morton wrote:
> > 
> > | "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> > | >
> > | > -	if(mca_system_init()) {
> > | > +	if (mca_system_init()) {
> > | >  		printk(KERN_ERR "MCA bus system initialisation failed\n");
> > | >  		return -ENODEV;
> > | >  	}
> > | >  
> > | > +	if (!MCA_bus)
> > | > +		return -ENODEV;
> > | 
> > | Why is it appropriate to register the MCA bus type when there is no
> > | MCA bus present?
> > 
> > Mostly because it was selected with CONFIG_MCA=y.
> > 
> > Another option (I think, need to test) is to check !MCA_bus
> > in drivers/mca/mca-legacy.c::find_mca_adapter(), so that
> > mca_bus_type isn't used when it shouldn't be.
> > 
> > Do you prefer that approach?
> 
> well my question really was a question, rather than a reimplementation
> suggestion.  If it _is_ appropriate that mca_bus_type be registered on a
> platform which is discovered to have no MCA hardware then fine.
> 
> Greg? James?  Any insights?

Ick, James is the one to answer here, as I remember this being pretty
messy at times due to the way the MCA code currently is...

thanks,

greg k-h

  reply	other threads:[~2004-05-17 22:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-17 21:46 [PATCH] init. mca_bus_type even if !MCA_bus Randy.Dunlap
2004-05-17 22:14 ` Andrew Morton
2004-05-17 22:08   ` Randy.Dunlap
2004-05-17 22:52     ` Andrew Morton
2004-05-17 22:58       ` Greg KH [this message]
2004-05-17 23:02       ` James Bottomley
2004-05-17 22:18   ` James Bottomley
2004-05-17 22:56     ` Andrew Morton

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=20040517225816.GA21333@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=james.bottomley@steeleye.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox