From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Mike Christie <michaelc@cs.wisc.edu>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
James Bottomley <James.Bottomley@suse.de>,
Jens Axboe <axboe@kernel.dk>, Boaz Harrosh <bharrosh@panasas.com>
Subject: Re: [RFC 22/22] tcm_loop: Add multi-fabric Linux/SCSI LLD fabric module
Date: Sun, 05 Sep 2010 14:51:19 -0700 [thread overview]
Message-ID: <1283723479.556.135.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20100905203006.GD18411@core.coreip.homeip.net>
On Sun, 2010-09-05 at 13:30 -0700, Dmitry Torokhov wrote:
> On Mon, Aug 30, 2010 at 02:23:23AM -0700, Nicholas A. Bellinger wrote:
> > +
> > +static void tcm_loop_primary_release(struct device *dev)
> > +{
> > + return;
> > +}
> > +
> > +static struct device tcm_loop_primary = {
> > + .init_name = "tcm_loop_0",
> > + .release = tcm_loop_primary_release,
> > +};
> > +
>
> No, you can not have statically allocated devices and dummy release
> functions.
>
Last time I checked this is still what mainline
drivers/scsi/scsi_debug.c is doing for struct device pseudo_primary:
static void pseudo_0_release(struct device *dev)
{
if (SCSI_DEBUG_OPT_NOISE & scsi_debug_opts)
printk(KERN_INFO "scsi_debug: pseudo_0_release() called\n");
}
static struct device pseudo_primary = {
.init_name = "pseudo_0",
.release = pseudo_0_release,
};
so for these type of things in TCM_Loop I tend to follow what scsi_debug does,
so I don't exactly see a issue here atm. Anybody else have comments..?
Best,
--nab
next prev parent reply other threads:[~2010-09-05 21:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 9:23 Nicholas A. Bellinger
2010-09-05 20:30 ` Dmitry Torokhov
2010-09-05 21:51 ` Nicholas A. Bellinger [this message]
2010-09-06 5:08 ` Dmitry Torokhov
2010-09-06 5:17 ` Greg KH
2010-09-06 5:21 ` Nicholas A. Bellinger
2010-09-06 5:38 ` Dmitry Torokhov
2010-09-06 6:01 ` Nicholas A. Bellinger
2010-09-06 6:26 ` Dmitry Torokhov
2010-09-06 14:48 ` Richard Sharpe
2010-09-06 15:06 ` Richard Sharpe
2010-09-06 19:44 ` Dmitry Torokhov
2010-09-06 20:34 ` Greg KH
2010-09-06 7:01 ` Dmitry Torokhov
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=1283723479.556.135.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@suse.de \
--cc=axboe@kernel.dk \
--cc=bharrosh@panasas.com \
--cc=dmitry.torokhov@gmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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®