public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	David Miller <davem@davemloft.net>,
	Roman Zippel <zippel@linux-m68k.org>,
	linux-scsi@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] new mac_scsi driver
Date: Fri, 25 Apr 2008 10:03:10 -0500	[thread overview]
Message-ID: <1209135790.3087.8.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0804251054200.2578@loopy.telegraphics.com.au>

On Fri, 2008-04-25 at 11:06 +1000, Finn Thain wrote:
> 
> On Thu, 24 Apr 2008, James Bottomley wrote:
> 
> > On Thu, 2008-04-24 at 23:08 +0200, Geert Uytterhoeven wrote:
> > > On Thu, 24 Apr 2008, Finn Thain wrote:
> > > > Replace the mac_esp driver with a new one based on the esp_scsi 
> > > > core.
> > > > 
> > > > For esp_scsi: add support for sync transfers for the PIO mode, add a 
> > > > new esp_driver_ops method to get the maximum dma transfer size (like 
> > > > the old NCR53C9x driver), and some cleanups.
> > > 
> > > Thanks!
> > > 
> > > I added this patch to my series, after fixing the few checkpatch.pl 
> > > issues and adding a test for MACH_IS_MAC() to esp_mac_probe().
> > 
> > I got the tabs and spaces thing.  I'm not too concerned about the 
> > assignment in conditional, but I'm happy to go whichever way the author 
> > does.
> 
> FWIW, I happen to disagree with checkpatch about the spaces following tabs 
> thing but I'm happy to follow convention. It did pick up on some other 
> things that I overlooked (Geert has fixed them).
> 
> > 
> > Could you repost please because I already have this queued, so I need a 
> > replacement (assuming everyone agrees).
> 
> Geert's version is fine with me:
> 
> http://linux-m68k-cvs.ubb.ca/~geert/linux-m68k-patches-2.6/m68k-new-mac_esp-driver.diff

It's a lot less easy to review stuff over the web (mainly, I'm afraid,
because people are lazy).

However, this:


> +static int __devinit esp_mac_probe(struct platform_device *dev)
> +{
> +	struct scsi_host_template *tpnt = &scsi_esp_template;
> +	struct Scsi_Host *host;
> +	struct esp *esp;
> +	int err;
> +	int chips_present;
> +	struct mac_esp_priv *mep;
> +
> +	if (!MACH_IS_MAC)
> +		return -ENODEV;

Looks strange ... it seems you have to do this because macintosh_config
which is used later can be uninitialised (i.e. pointing to rubbish) if
it's not set?

James



  reply	other threads:[~2008-04-25 15:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24  7:30 [PATCH] new mac_scsi driver Finn Thain
2008-04-24  7:56 ` David Miller
2008-04-24 21:08 ` Geert Uytterhoeven
2008-04-24 21:33   ` James Bottomley
2008-04-25  1:06     ` Finn Thain
2008-04-25 15:03       ` James Bottomley [this message]
2008-04-25 19:43         ` Geert Uytterhoeven

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=1209135790.3087.8.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=davem@davemloft.net \
    --cc=fthain@telegraphics.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=zippel@linux-m68k.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