public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] further sim710 updates
Date: Mon, 10 Feb 2003 16:32:28 +0100	[thread overview]
Message-ID: <20030210163228.A14769@lst.de> (raw)
In-Reply-To: <1044890849.2008.71.camel@mulgrave>; from James.Bottomley@steeleye.com on Mon, Feb 10, 2003 at 09:27:27AM -0600

On Mon, Feb 10, 2003 at 09:27:27AM -0600, James Bottomley wrote:
> On Mon, 2003-02-10 at 01:59, Christoph Hellwig wrote:
> > and I think there's more that should be done, but this would change
> > user-visiable attributes:
> > 
> >   - remove the ugly single module option code and the command line
> >     parsing in favour of Rusty's new module_param stuff
> >   - split the driver into two drivers: 53c700_eisa and 53c700_mca.
> >     There's no logic shared between those two busses, just a little
> >     bit of helper in the setup/remove code
> 
> Sounds good if you want to do a patch.

This will be in the next patch revision.

> >   - mca_register_driver/mca_unregister_driver should check for
> >     the precense of an MCA bus by themselves instead of leaving
> >     it to the caller
> 
> The if(MCA_bus) is unnecessary.  If there's no MCA bus, no IDs will be
> stored, so nothing will get attached.

Ok.

> >   - mca_register_driver/mca_unregister_driver should be named
> >     mca_driver_register/mca_driver_unregister to be more similar
> >     to the other *driver_(un)registers.
> 
> Which others?  I modelled the interface on PCI, which has
> pci_register_driver() etc.  I agree on standardisation, but the way I
> did it was standard when the MCA bus code was written...

eisa and the plain, non-prefix versions.  Okay, maybe MCA is okay, but
at least it's inconsistant..

> > @@ -32,51 +32,18 @@
> >  #include <linux/blk.h>
> >  #include <linux/device.h>
> >  #include <linux/init.h>
> > -#ifdef CONFIG_MCA
> >  #include <linux/mca.h>
> > -#endif
> 
> This can't be done otherwise the driver won't compile on non x86 archs
> (yes, I know, I'll fix the MCA header file...)

If I split the EISA/MCA parts into separate driver we won't have that
problem anymore.


      reply	other threads:[~2003-02-10 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10  7:59 [PATCH] further sim710 updates Christoph Hellwig
2003-02-10 15:27 ` James Bottomley
2003-02-10 15:32   ` Christoph Hellwig [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=20030210163228.A14769@lst.de \
    --to=hch@lst.de \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@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