From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/4] scsi: remove usage of proc_name from scsi_host_alloc
Date: Sun, 13 Nov 2005 17:52:13 +0100 [thread overview]
Message-ID: <43776F3D.4060205@s5r6.in-berlin.de> (raw)
In-Reply-To: <43776EA3.3010607@s5r6.in-berlin.de>
I wrote:
> Christoph Hellwig wrote:
>> ->name is not mandatory. You may just implement ->info
>
> No, ->info is optional according to a current comment, and according to
> the implementation as far as I have seen.
>
> Also, ->name is used in a number of places if some other host template
> members are not provided, i.e. it is practically mandatory.
PS: name can be (and is) used in place of info, but info can hardly be
used instead of name because name is shorter.
--
Stefan Richter
-=====-=-=-= =-== -==-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2005-11-13 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 16:17 [PATCH 2/4] scsi: remove usage of proc_name from scsi_host_alloc Stefan Richter
2005-11-13 16:42 ` Christoph Hellwig
2005-11-13 16:49 ` Stefan Richter
2005-11-13 16:52 ` Stefan Richter [this message]
2005-11-13 17:07 ` Christoph Hellwig
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=43776F3D.4060205@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox