From: Christoph Hellwig <hch@infradead.org>
To: Dave Boutcher <sleddog@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] ibmvscsi driver - next version
Date: Mon, 23 Feb 2004 19:49:13 +0000 [thread overview]
Message-ID: <20040223194913.A13181@infradead.org> (raw)
In-Reply-To: <opr3t8zmyel6e53g@us.ibm.com>; from sleddog@us.ibm.com on Mon, Feb 23, 2004 at 01:41:36PM -0600
On Mon, Feb 23, 2004 at 01:41:36PM -0600, Dave Boutcher wrote:
> > any reason you hid all headers in ibmvscsi.h? normally we include
> > them in the source files directly.
>
> Philosophy question....I usually assume that a header file should in turn
> include anything it needs...so ibmvscsi.h includes all the scsi header
> files it uses...bad philosophy?
If you actually need them you need to include them. But in ibmvscsi.h
I only see pointers to the scsi datastructures - for those a simple
forward-declaration is enough.
> > This can't ever happen. You will only get called for commands
> > that you have accepted in queuecommand and not called the completion
> > routine for.
>
> The above code was in the abort routine....I would personally prefer to
> leave the check in there from pure paranoia. If we are into aborts, bad
> things are happening, and I don't really care about code path in
> abort...perhaps I should add a "this should never happen" comment? :-) I
> could make it a BUG()...I'm not a huge fan of BUG() in drivers...
Just remove it. If you don't trust the midlayer it's hard to write
a scsi driver..
> The INIT_WORK call needs to be done before we get back to the subdriver in
> case the first message gets turned around really fast. Having this stub
> seemed the cleanest way to handle that generically.
Why can't you simply do it in ibmvscsi_init_crq_queue for example?
next prev parent reply other threads:[~2004-02-23 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 4:24 [PATCH] ibmvscsi driver - next version Dave Boutcher
2004-02-23 14:45 ` Christoph Hellwig
2004-02-23 19:41 ` Dave Boutcher
2004-02-23 19:49 ` Christoph Hellwig [this message]
2004-02-23 20:52 ` Brian King
2004-02-23 21:08 ` Christoph Hellwig
2004-02-23 22:08 ` Mike Anderson
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=20040223194913.A13181@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sleddog@us.ibm.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