From: Bart Van Assche <bvanassche@acm.org>
To: Hannes Reinecke <hare@suse.de>,
James Bottomley <jbottomley@parallels.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 7/7] scsi_error: do not use command list for host reset
Date: Fri, 27 Jun 2014 09:06:15 +0200 [thread overview]
Message-ID: <53AD17E7.8080002@acm.org> (raw)
In-Reply-To: <1403850425-89297-8-git-send-email-hare@suse.de>
On 06/27/14 08:27, Hannes Reinecke wrote:
> * scsi_eh_host_reset - send a host reset
> + * @shost: &scsi host being recovered.
In "Documentation/kernel-doc-nano-HOWTO.txt" I found "'&struct_name' -
name of a structure (up to two words including 'struct')". This made me
wonder whether the ampersand was added on purpose in the
scsi_eh_host_reset() kernel-doc header ?
Bart.
next prev parent reply other threads:[~2014-06-27 7:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 6:26 [PATCH 0/7] Use 'Scsi_Host' as argument for host reset Hannes Reinecke
2014-06-27 6:26 ` [PATCH 1/7] scsi: fix comment in scsi_device_set_state() Hannes Reinecke
2014-06-27 6:27 ` [PATCH 2/7] mptfc: Do not call fc_block_scsi_eh() on host reset Hannes Reinecke
2014-06-27 6:27 ` [PATCH 3/7] ibmvfc: " Hannes Reinecke
2014-06-27 6:27 ` [PATCH 4/7] libfc: " Hannes Reinecke
2014-06-27 6:27 ` [PATCH 5/7] scsi_transport_fc: Use fc_rport as argument for fc_block_scsi_eh Hannes Reinecke
2014-06-27 12:46 ` Steffen Maier
2014-06-27 6:27 ` [PATCH 6/7] scsi: Use Scsi_Host as argument for eh_host_reset_handler Hannes Reinecke
2014-06-27 10:47 ` Steffen Maier
2014-06-27 11:04 ` Hannes Reinecke
2014-06-27 11:52 ` Martin Peschke
2014-06-27 12:00 ` Hannes Reinecke
2014-06-27 14:41 ` Steffen Maier
2014-06-27 17:52 ` Hannes Reinecke
2014-06-27 6:27 ` [PATCH 7/7] scsi_error: do not use command list for host reset Hannes Reinecke
2014-06-27 7:06 ` Bart Van Assche [this message]
2014-06-27 7:58 ` Christoph Hellwig
2014-06-27 10:42 ` Steffen Maier
2014-06-27 7:59 ` [PATCH 0/7] Use 'Scsi_Host' as argument " Christoph Hellwig
2014-06-27 8:14 ` Hannes Reinecke
2014-06-27 8:15 ` Christoph Hellwig
2014-09-07 16:21 ` Christoph Hellwig
2014-09-08 6:49 ` Hannes Reinecke
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=53AD17E7.8080002@acm.org \
--to=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.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.