From: Greg KH <gregkh@suse.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Richard Sharpe <realrichardsharpe@gmail.com>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
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: Mon, 6 Sep 2010 13:34:19 -0700 [thread overview]
Message-ID: <20100906203419.GF5162@suse.de> (raw)
In-Reply-To: <20100906194446.GA31384@core.coreip.homeip.net>
On Mon, Sep 06, 2010 at 12:44:46PM -0700, Dmitry Torokhov wrote:
> Yes, that is the one. I'll blame Greg for inconsistent naming that
> caused this error :) - we usually have xxx_register() for objects that
> we already have on hand and xxx_create() (as in device_create) when we
> want the object to be allocated for us.
Yes, we have a number of naming inconsistancies in the driver core like
this. I need to sit down and fix them all one of these days...
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-06 20:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 9:23 [RFC 22/22] tcm_loop: Add multi-fabric Linux/SCSI LLD fabric module Nicholas A. Bellinger
2010-09-05 20:30 ` Dmitry Torokhov
2010-09-05 21:51 ` Nicholas A. Bellinger
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 14:48 ` Richard Sharpe
2010-09-06 15:06 ` Richard Sharpe
2010-09-06 15:06 ` Richard Sharpe
2010-09-06 19:44 ` Dmitry Torokhov
2010-09-06 20:34 ` Greg KH [this message]
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=20100906203419.GF5162@suse.de \
--to=gregkh@suse.de \
--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 \
--cc=nab@linux-iscsi.org \
--cc=realrichardsharpe@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.