public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: nab@kernel.org
Cc: linux-iscsi-target-dev@googlegroups.com,
	LKML <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Christoph Hellwig <hch@lst.de>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Hannes Reinecke <hare@suse.de>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [Announce]: Target_Core_Mod/ConfigFS and LIO-Target v3.0 work
Date: Sat, 13 Dec 2008 01:20:05 -0500	[thread overview]
Message-ID: <54939.1229149205@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 12 Dec 2008 01:40:09 PST." <1229074809.4153.666.camel@haakon2.linux-iscsi.org>

[-- Attachment #1: Type: text/plain, Size: 493 bytes --]

On Fri, 12 Dec 2008 01:40:09 PST, "Nicholas A. Bellinger" said:

> Too bad, because you are missing out on the most advanced ConfigFS
> enabled storage engine on the planet.

OK. I *have* to ask.. ;)

What's the *second* most advanced configfs-enabled storage engine?

The only in-tree users of configfs I could find (grepping for the string
'config_item_init') were drivers/net/netconsole, fs/ocfs2, and fs/dlm, so
"most advanced configfs" is well into "world's tallest midget" territory...


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2008-12-13  6:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  3:14 [Announce]: Target_Core_Mod/ConfigFS and LIO-Target v3.0 work Nicholas A. Bellinger
2008-12-11 19:24 ` Bart Van Assche
2008-12-11 19:58   ` Nicholas A. Bellinger
2008-12-12  7:21     ` Bart Van Assche
2008-12-12  9:40       ` Nicholas A. Bellinger
2008-12-13  6:20         ` Valdis.Kletnieks [this message]
2008-12-13  8:27           ` Nicholas A. Bellinger
2008-12-13  9:41           ` Bart Van Assche
     [not found]             ` <1229162907.4153.857.camel@haakon2.linux-iscsi.org>
     [not found]               ` <e2e108260812130223q13fd98d8gc1e55881a92b939@mail.gmail.com>
2008-12-13 11:18                 ` Nicholas A. Bellinger
2008-12-13 11:56                   ` Bart Van Assche
2008-12-13 12:33                     ` Nicholas A. Bellinger
     [not found]                       ` <e2e108260812130450y3288b32av7f435544823d9e97@mail.gmail.com>
2008-12-13 13:14                         ` Nicholas A. Bellinger
2008-12-13 15:24                     ` James Bottomley
2008-12-13 22:50                       ` Nicholas A. Bellinger
2008-12-14 16:53                         ` Bart Van Assche
2008-12-16 18:45                       ` Vladislav Bolkhovitin
2008-12-13 15:35                   ` Vladislav Bolkhovitin

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=54939.1229149205@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-iscsi-target-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=nab@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