From: Christoph Hellwig <hch@infradead.org>
To: Naveen Burmi <naveenb@cisco.com>
Cc: linux-scsi@vger.kernel.org, davmyers@cisco.com
Subject: Re: Request for review of Linux iSCSI driver version 4.0.0.2
Date: Fri, 28 Nov 2003 12:03:38 +0000 [thread overview]
Message-ID: <20031128120338.A8954@infradead.org> (raw)
In-Reply-To: <03112816062402.31165@naveenb-lnx.cisco.com>; from naveenb@cisco.com on Fri, Nov 28, 2003 at 04:06:24PM +0530
> 2. iscis-kernel.h:
> - only backward-compat cruft, should go away.
still too much left. the file should really be empty..
e.g. the HAS_ ifdefs should just go away, dito for all those
macros that aren't needed.
> 8. - host and hba can't be NULL in ->queuecommand per defintion,
> similarly id, lun cdbsize and use_sg can't be bigger than you
> set in the template.
BUG_ON(host == NULL); isn't needed either, you'd get the same oops
when dereferencing a NULL pointer two lines later.
> 10. - the procfs code is a mess. Please move it over to
> proper per-device / per-host sysfs attributes as procfs
> support in HBA drivers is deprecated.
please don't add an attribute group, just use the shost_attrs field
in the host template. iscsi_show_device() doesn't look like a good
idea, what about adding an iscsi pseudo device as parent to identify
the device as iscsi in sysfs?
This whole find_keyword business is not good. sysfs files are
supposed to have a single value. We should probably do some
brainstorming on the right API for this..
next prev parent reply other threads:[~2003-11-28 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 10:36 Request for review of Linux iSCSI driver version 4.0.0.2 Naveen Burmi
2003-11-28 12:03 ` Christoph Hellwig [this message]
2003-12-01 10:46 ` Surekha.PC
2003-12-01 15:38 ` 'Christoph Hellwig'
2003-12-01 15:40 ` James Bottomley
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=20031128120338.A8954@infradead.org \
--to=hch@infradead.org \
--cc=davmyers@cisco.com \
--cc=linux-scsi@vger.kernel.org \
--cc=naveenb@cisco.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