linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: "James E.J. Bottomley" <JBottomley@parallels.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] scsi: Some seq_file cleanups/optimizations
Date: Sun, 30 Nov 2014 17:40:31 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LNX.2.00.1411301709120.4858@nippy.intranet> (raw)
In-Reply-To: <1417221258-4937-1-git-send-email-linux@rasmusvillemoes.dk>


On Sat, 29 Nov 2014, Rasmus Villemoes wrote:

> These patches mostly replace seq_printf with simpler and faster 
> equivalents, e.g. seq_printf(m, "something") => seq_puts(m, "something") 
> and seq_printf(m, "\n") => seq_putc(m, '\n). But before my Coccinelle 
> scripts could be unleashed I had to clean up some unnecessary, and in 
> the PRINTP case quite obfuscating, macros.

Nice cleanup.

FYI, the PRINTP and *_RELEASE macros and others have been removed already 
as part of a patch series that covers all of the NCR5380 drivers.

That patch series is queued for v3.19: 
git://git.infradead.org/users/hch/scsi-queue.git drivers-for-3.19

Some of your patches to NCR5380.c, atari_NCR5380.c, g_NCR5380.c, 
sun3_NCR5380.c will not apply to that branch.

It isn't my job to resolve merge conflicts, but seeing as the patches you 
sent were generated by Coccinelle scripts then perhaps it would be better 
to re-run them against the drivers branch (?)

> 
> The patches don't change the semantics of the code (well, that's the
> idea anyway), but should make it slightly smaller and faster.
> 
> Rasmus Villemoes (7):
>   scsi: Remove SPRINTF macro
>   scsi/g_NCR5380: Remove obfuscating macros
>   scsi/advansys: Replace seq_printf with seq_puts
>   scsi/aha152x: Replace seq_printf with seq_puts
>   scsi: misc:  Replace seq_printf with seq_puts
>   scsi: misc: Merge consecutive seq_puts calls
>   scsi: misc: Print single-character strings with seq_putc
> 
>  drivers/scsi/BusLogic.c             |  10 +-
>  drivers/scsi/NCR5380.c              |  42 +++--
>  drivers/scsi/advansys.c             | 145 ++++++++---------
>  drivers/scsi/aha152x.c              | 301 ++++++++++++++++++------------------
>  drivers/scsi/aic7xxx/aic79xx_proc.c |  38 +++--
>  drivers/scsi/aic7xxx/aic7xxx_proc.c |  24 +--
>  drivers/scsi/arm/fas216.c           |   6 +-
>  drivers/scsi/atari_NCR5380.c        |   4 +-
>  drivers/scsi/atp870u.c              |   5 +-
>  drivers/scsi/dc395x.c               |  78 +++++-----
>  drivers/scsi/dpt_i2o.c              |   2 +-
>  drivers/scsi/eata_pio.c             |   2 +-
>  drivers/scsi/esas2r/esas2r_main.c   |   2 +-
>  drivers/scsi/g_NCR5380.c            |  66 ++++----
>  drivers/scsi/gdth_proc.c            |  24 +--
>  drivers/scsi/in2000.c               |  18 +--
>  drivers/scsi/ips.c                  |   7 +-
>  drivers/scsi/megaraid.c             |   2 +-
>  drivers/scsi/nsp32.c                |  41 +++--
>  drivers/scsi/pcmcia/nsp_cs.c        |  50 +++---
>  drivers/scsi/qla2xxx/qla_dfs.c      |   8 +-
>  drivers/scsi/scsi_proc.c            |  22 +--
>  drivers/scsi/scsi_trace.c           |   6 +-
>  drivers/scsi/sun3_NCR5380.c         |   4 +-
>  drivers/scsi/wd33c93.c              |  18 +--
>  drivers/scsi/wd7000.c               |  41 +++--
>  26 files changed, 460 insertions(+), 506 deletions(-)
> 
> 

-- 

  parent reply	other threads:[~2014-11-30  6:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29  0:34 [PATCH 0/7] scsi: Some seq_file cleanups/optimizations Rasmus Villemoes
2014-11-29  0:34 ` [PATCH 1/7] scsi: Remove SPRINTF macro Rasmus Villemoes
2014-11-29  0:34 ` [PATCH 2/7] scsi/g_NCR5380: Remove obfuscating macros Rasmus Villemoes
2014-11-29  0:34 ` [PATCH 3/7] scsi/advansys: Replace seq_printf with seq_puts Rasmus Villemoes
2014-11-29  0:34 ` [PATCH 4/7] scsi/aha152x: " Rasmus Villemoes
2014-11-29  0:34 ` [PATCH 5/7] scsi: misc: " Rasmus Villemoes
2014-11-29  0:34 ` [PATCH 6/7] scsi: misc: Merge consecutive seq_puts calls Rasmus Villemoes
2014-11-29  0:34 ` [PATCH 7/7] scsi: misc: Print single-character strings with seq_putc Rasmus Villemoes
2014-11-30  6:40 ` Finn Thain [this message]
2014-12-02 23:10 ` [PATCH v2 0/6] scsi: Some seq_file cleanups/optimizations Rasmus Villemoes
2014-12-02 23:10   ` [PATCH v2 1/6] scsi: Remove SPRINTF macro Rasmus Villemoes
2015-01-30  1:37     ` Finn Thain
2014-12-02 23:10   ` [PATCH v2 2/6] scsi/advansys: Replace seq_printf with seq_puts Rasmus Villemoes
2015-01-30  1:38     ` Finn Thain
2014-12-02 23:10   ` [PATCH v2 3/6] scsi/aha152x: " Rasmus Villemoes
2015-01-30  1:40     ` Finn Thain
2014-12-02 23:10   ` [PATCH v2 4/6] scsi: misc: " Rasmus Villemoes
2015-01-30  1:41     ` Finn Thain
2014-12-02 23:10   ` [PATCH v2 5/6] scsi: misc: Merge consecutive seq_puts calls Rasmus Villemoes
2015-01-30  1:42     ` Finn Thain
2014-12-02 23:10   ` [PATCH v2 6/6] scsi: misc: Print single-character strings with seq_putc Rasmus Villemoes
2015-01-30  1:44     ` Finn Thain
2015-01-21 12:08   ` [PATCH v2 0/6] scsi: Some seq_file cleanups/optimizations Rasmus Villemoes
2015-01-29  6:56   ` Finn Thain
2015-01-29  9:16     ` Rasmus Villemoes
2015-01-29 14:22       ` Steven Rostedt

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=alpine.LNX.2.00.1411301709120.4858@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=JBottomley@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /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;
as well as URLs for NNTP newsgroup(s).