public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Finn Thain <fthain@telegraphics.com.au>,
	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: Thu, 24 Apr 2008 16:33:27 -0500	[thread overview]
Message-ID: <1209072808.3121.22.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0804242307370.21224@anakin>

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.

Could you repost please because I already have this queued, so I need a
replacement (assuming everyone agrees).  There are other issues with the
driver (like the dma_length_limit stuff which looks like it should
really by fixed using the block layer segment boundary/segment length
limits, but that's more esp generic than mac_esp specific) which I
planned to look into after it was merged.

Thanks,

James



  reply	other threads:[~2008-04-24 21:33 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 [this message]
2008-04-25  1:06     ` Finn Thain
2008-04-25 15:03       ` James Bottomley
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=1209072808.3121.22.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