From: "'Christoph Hellwig'" <hch@infradead.org>
To: "Mukker, Atul" <atulm@lsil.com>
Cc: "'Mike Anderson'" <andmike@us.ibm.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: unique entry points for all driver hosts
Date: Tue, 13 May 2003 16:09:02 +0100 [thread overview]
Message-ID: <20030513160902.A26759@infradead.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570185F196@EXA-ATLANTA.se.lsil.com>; from atulm@lsil.com on Tue, May 13, 2003 at 09:43:52AM -0400
On Tue, May 13, 2003 at 09:43:52AM -0400, Mukker, Atul wrote:
> IMHO, declaring multiple SHTs as suggested by Christoph Hellwig may not be a
> good idea since it might appear like a hack, would lose the "template"
> ideology and is not object-oriented :-)
The linux kernel is a pragmatic mix of procedural and object oriented
concepts, if you want ideology please look elsewhere. The template is
exactly a template for multiple hosts and if you driver supports different
enouigh boards you need multiple templates - it's pretty simple. Not that
the template is used much at all..
> Host structure would be best place to have pointers to these hooks as well.
This is right but not how the linux scsi stack was written. Removing them
now causes more pain then it would solve - just live with the extra indirection.
next prev parent reply other threads:[~2003-05-13 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 13:43 Mukker, Atul
2003-05-13 15:09 ` 'Christoph Hellwig' [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 22:41 Mukker, Atul
2003-05-12 23:38 ` Mike Anderson
2003-05-13 5:37 ` 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=20030513160902.A26759@infradead.org \
--to=hch@infradead.org \
--cc=andmike@us.ibm.com \
--cc=atulm@lsil.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®