From: Patrick Mansfield <patmans@us.ibm.com>
To: Luben Tuikov <luben@splentec.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] SCSI Core cmd allocation 3/3
Date: Mon, 13 Jan 2003 12:11:29 -0800 [thread overview]
Message-ID: <20030113121129.A16510@beaverton.ibm.com> (raw)
In-Reply-To: <3E2310A0.8080308@splentec.com>; from luben@splentec.com on Mon, Jan 13, 2003 at 02:16:48PM -0500
On Mon, Jan 13, 2003 at 02:16:48PM -0500, Luben Tuikov wrote:
> Christoph Hellwig wrote:
> >
> > Well, where do you actually _need_ scsi_get_command(), that's the question.
> >
> > I see the purpose, but I don't see it actually used.
>
> The scsi devices discovery code *may* use it.
Then do so in another patch.
> If a global variable is used in a couple of files, belonging
> to the same functionality, providing a unified service, and if
> there's more than one of them, then they are better organized
> as such as I've outlined.
Then move all the scsi globals into it. But, that should be a separate
patch.
> > and stuff like:
> >
> > + if (!dev) return NULL;
> > + if (!dev->host) return NULL;
> >
> > doesn't even seem to be K&R to me :)
>
> Christoph, please, this is an *inline* function -- it doesn't have to be
> 20 lines if it can be 10.
You should match the other kernel code as much as possible, it makes it
easier for other kernel developers to read it.
-- Patrick Mansfield
next prev parent reply other threads:[~2003-01-13 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 0:37 [PATCH] SCSI Core cmd allocation 3/3 Luben Tuikov
2003-01-11 18:03 ` Christoph Hellwig
2003-01-13 17:12 ` Luben Tuikov
2003-01-13 17:59 ` Christoph Hellwig
2003-01-13 19:16 ` Luben Tuikov
2003-01-13 20:11 ` Patrick Mansfield [this message]
2003-01-13 20:40 ` Luben Tuikov
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=20030113121129.A16510@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben@splentec.com \
/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