From: Sam Creasey <sammy@sammy.net>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: "James E.J. Bottomley" <JBottomley@parallels.com>,
linux-scsi@vger.kernel.org, Sam Creasey <sammy@sammy.net>,
Russell King <linux@arm.linux.org.uk>,
Michael Schmitz <schmitz@debian.org>,
Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-m68k@vger.kernel.org
Subject: Re: [PATCH v2 00/12] scsi/NCR5380: fix debugging macros and #include structure
Date: Fri, 11 Apr 2014 10:39:01 -0400 [thread overview]
Message-ID: <20140411143900.GG21346@anhedonia> (raw)
In-Reply-To: <20140319123516.542623278@telegraphics.com.au>
Acked-by: Sam Creasey <sammy@sammy.net>
On Wed, Mar 19, 2014 at 11:35:16PM +1100, Finn Thain wrote:
>
> This patch series addresses several issues with NCR5380 drivers:
>
> 1. The complex network of #include directives.
>
> 2. Three inconsistent implementations of the core driver all attempting
> to share the same macro definitions in NCR5380.h.
>
> 3. Broken debugging code.
>
> In the past these issues have led to compiler warnings and ugly hacks to
> fix build failures.
>
> This patch series fixes the debugging code by reducing the divergence
> between the various core driver implementations.
>
> The final two patches in the series further reduce divergence by refactoring
> sun3_scsi.c and sun3_scsi_vme.c so that they follow the same structure as
> the other NCR5380 drivers.
>
> By the end of this patch series over 800 net lines of code have been
> removed. This is mostly duplicated code that's easily eliminated once the
> debugging code is made consistent (and some dead code is removed).
>
> Better uniformity and less duplication should assist future work such as
> modernization and trivial clean-up.
>
> To make code review easier I've tried to keep these patches succinct and
> free of extraneous changes. Though I did run checkpatch.pl, I've ignored
> whitespace issues in existing code. I will send separate patches for
> whitespace clean-up of NCR5380 drivers.
>
> All NCR5380 drivers have been compile-tested with this patch series:
> arm/cumana_1.c
> arm/oak.c
> atari_scsi.c
> dmx3191d.c
> dtc.c
> g_NCR5380.c
> g_NCR5380_mmio.c
> mac_scsi.c
> pas16.c
> sun3_scsi.c
> sun3_scsi_vme.c
> t128.c
>
> I've successfully regression tested this patch series using mac_scsi on a
> PowerBook 180. The debugging macros are now usable again.
next prev parent reply other threads:[~2014-04-11 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 12:35 [PATCH v2 00/12] scsi/NCR5380: fix debugging macros and #include structure Finn Thain
2014-03-19 12:35 ` [PATCH v2 01/12] scsi/NCR5380: remove unused BOARD_NORMAL and BOARD_NCR53C400 Finn Thain
2014-03-19 12:35 ` [PATCH v2 02/12] scsi/NCR5380: remove redundant HOSTS_C macro tests Finn Thain
2014-03-19 12:35 ` [PATCH v2 03/12] scsi/NCR5380: remove old CVS keywords Finn Thain
2014-03-19 12:35 ` [PATCH v2 04/12] scsi/NCR5380: use NCR5380_dprint() instead of NCR5380_print() Finn Thain
2014-03-19 12:35 ` [PATCH v2 05/12] scsi/NCR5380: fix build failures when debugging is enabled Finn Thain
2014-03-19 12:35 ` [PATCH v2 06/12] scsi/NCR5380: fix dprintk macro usage and definition Finn Thain
2014-03-19 12:35 ` [PATCH v2 07/12] scsi/NCR5380: adopt NCR5380_dprint() and NCR5380_dprint_phase() Finn Thain
2014-04-26 1:51 ` Michael Schmitz
2014-03-19 12:35 ` [PATCH v2 08/12] scsi/NCR5380: adopt dprintk() Finn Thain
2014-04-26 1:52 ` Michael Schmitz
2014-03-19 12:35 ` [PATCH v2 09/12] scsi/NCR5380: fix and standardize NDEBUG macros Finn Thain
2014-03-19 12:35 ` [PATCH v2 10/12] scsi/NCR5380: remove unused macro definitions Finn Thain
2014-04-26 1:53 ` Michael Schmitz
2014-03-19 12:35 ` [PATCH v2 11/12] scsi/NCR5380: reduce depth of sun3_scsi nested includes Finn Thain
2014-03-19 12:35 ` [PATCH v2 12/12] scsi/NCR5380: merge sun3_scsi_vme.c into sun3_scsi.c Finn Thain
2014-04-11 14:39 ` Sam Creasey [this message]
2014-04-26 17:21 ` [PATCH v2 00/12] scsi/NCR5380: fix debugging macros and #include structure James Bottomley
2014-04-29 2:22 ` Finn Thain
2014-04-29 3:15 ` Michael Schmitz
2014-04-29 14:41 ` James Bottomley
2014-04-30 7:45 ` Michael Schmitz
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=20140411143900.GG21346@anhedonia \
--to=sammy@sammy.net \
--cc=JBottomley@parallels.com \
--cc=fthain@telegraphics.com.au \
--cc=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=schmitz@debian.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