From: James Bottomley <James.Bottomley@SteelEye.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Rob Landley <rob@landley.net>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 15/15] Add Documentation/DocBook/scsi_midlayer.tmpl and add to Makefile.
Date: Sat, 27 Oct 2007 08:24:24 -0500 [thread overview]
Message-ID: <1193491464.15612.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20071026230557.2ac5f9c8.rdunlap@xenotime.net>
On Fri, 2007-10-26 at 23:05 -0700, Randy Dunlap wrote:
> On Fri, 26 Oct 2007 23:18:00 -0500 Rob Landley wrote:
>
> > From: Rob Landley <rob@landley.net>
> >
> > Add Documentation/DocBook/scsi_midlayer.tmpl and add to Makefile.
>
>
> I have comments for all 15 patches here.
>
> a. You should cc: the maintainer who you want/expect to apply the
> patches. Always. Andrew Morton is the only person who
> trolls for patches on a mailing list. :)
Realistically too, for this first batch that covers mostly the mid-layer
and the transport classes, a single patch like you originally submitted
was just fine. One patch per file isn't. Patches should be split
across functional areas (in this case the function is simply adding the
SCSI mid layer to the docbook build, so they can all go together).
> b. The function "Description:" section header is not strictly
> required by scripts/kernel-doc. It will assume that the
> first text section after parameters is the Description:
> section. FYI.
>
> c. Extraneous whitespace. Git or quilt check for this.
> I don't know about hg...
Actually, the checkpatch.pl script in the scripts directory of the
kernel is very good for this (I ran it on the original monolithic
patch):
jejb@mulgrave> ./scripts/checkpatch.pl ~/tmp.mail
ERROR: trailing whitespace
#1065: FILE: drivers/scsi/scsi_ioctl.c:185:
+ * a pointer to a &struct scsi_device. $
ERROR: trailing whitespace
#1670: FILE: drivers/scsi/scsicam.c:60:
+ * Description : determine the BIOS mapping/geometry used for a drive
in a $
total: 2 errors, 0 warnings, 1502 lines checked
Your patch has style problems, please review. If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
In addition, there seem to be a few functions that you added kerneldoc
for which don't show up in the doc output. The one that caught my eye
was scsi_cmd_get_serial(), but I think there are others.
James
next prev parent reply other threads:[~2007-10-27 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 4:18 [PATCH 15/15] Add Documentation/DocBook/scsi_midlayer.tmpl and add to Makefile Rob Landley
2007-10-27 6:05 ` Randy Dunlap
2007-10-27 13:24 ` James Bottomley [this message]
2007-10-27 23:53 ` Rob Landley
2007-10-29 10:12 ` Rob Landley
2007-11-03 2:28 ` James Bottomley
[not found] ` <200711031330.39906.rob@landley.net>
[not found] ` <20071104100252.c3e08c71.rdunlap@xenotime.net>
2007-11-07 6:47 ` [PATCH] Add Documentation/DocBook/scsi_midlayer.tmpl and update kerneldoc comments and Makefile James Bottomley
2007-11-08 20:19 ` Rob Landley
2007-11-15 23:42 ` [PATCH] scsi: docbook and kernel-doc updates Randy Dunlap
2007-11-16 3:23 ` Rob Landley
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=1193491464.15612.6.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.net \
/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