All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Kashyap, Desai" <kashyap.desai@lsi.com>
Cc: linux-scsi@vger.kernel.org, Eric.Moore@lsi.com, Sathya.Prakash@lsi.com
Subject: Re: [PATCH 22/24] mpt fusion: [2.6.30-rc6]Added support for Broadcast primitives Event handling
Date: Wed, 27 May 2009 19:27:49 +0000	[thread overview]
Message-ID: <1243452469.6067.49.camel@localhost.localdomain> (raw)
In-Reply-To: <20090522111109.GP16331@lsi.com>

On Fri, 2009-05-22 at 16:41 +0530, Kashyap, Desai wrote:
> @@ -4314,6 +4333,182 @@ mptsas_send_raid_event(struct fw_event_work *fw_event)
>  		mptsas_free_fw_event(ioc, fw_event);
>  }
>  
> +/**
> + *	mptsas_issue_tm - send mptsas internal tm request
> + *	@ioc: Pointer to MPT_ADAPTER structure
> + *	@type
> + *	@channel
> + *	@id
> + *	@lun
> + *	@task_context
> + *	@timeout
> + *
> + *	return:
> + *
> + **/

That's not really very descriptive, is it?

> +/**
> + * mptscsih_get_scsi_lookup
> + *
> + * retrieves scmd entry from ScsiLookup[] array list
> + *
> + * @ioc: Pointer to MPT_ADAPTER structure
> + * @i: index into the array
> + *
> + * Returns the scsi_cmd pointer
> + *
> + **/

This is nicely descriptive, but it isn't legal docbook.  That should be

/**
 * mptscsih_get_scsi_lookup - retrieve scmd entry from ScsiLookup[] array list
 * @ioc: Pointer to MPT_ADAPTER structure
 * @i: index into the array
etc...

Nor is this:

> +/**
> + *     mptsas_broadcast_primative_work - Work queue thread to handle
> + *     broadcast primitive events
> + *     @work: work queue payload containing info describing the event
> + *
> + **/

The initial description needs to be all on one line, not split across
two.

James



James



      reply	other threads:[~2009-05-27 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 11:11 [PATCH 22/24] mpt fusion: [2.6.30-rc6]Added support for Broadcast primitives Event handling Kashyap, Desai
2009-05-27 19:27 ` James Bottomley [this message]

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=1243452469.6067.49.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=Eric.Moore@lsi.com \
    --cc=Sathya.Prakash@lsi.com \
    --cc=kashyap.desai@lsi.com \
    --cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.