From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: linux-iscsi-target-dev@googlegroups.com
Cc: 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: Fri, 12 Dec 2008 08:21:08 +0100 [thread overview]
Message-ID: <e2e108260812112321w2f5b1827xe2593888e44808ae@mail.gmail.com> (raw)
In-Reply-To: <1229025513.4153.542.camel@haakon2.linux-iscsi.org>
On Thu, Dec 11, 2008 at 8:58 PM, Nicholas A. Bellinger
<nab@linux-iscsi.org> wrote:
>
> On Thu, 2008-12-11 at 20:24 +0100, Bart Van Assche wrote:
>> On Thu, Dec 11, 2008 at 4:14 AM, Nicholas A. Bellinger
>> <nab@linux-iscsi.org> wrote:
>> > Things are moving quickly for Target_Core_Mod/ConfigFS and LIO-Target
>> > v3.0 development, and I invite folks to have a look at the code. To
>> > dive into the rest of the v3.0 code via git-web, check out:
>> >
>> > http://git.kernel.org/?p=linux/kernel/git/nab/lio-core-2.6.git;a=tree;f=drivers/lio-core
>>
>> I didn't have a look at the LIO code, but I ran it through checkpatch.
>> The result summary is as follows:
>>
> Thanks for the note, but checkpatch output on the entire tree (not just
> the patchs I posted) does not really help the discussion. Obviously
> this is on my list before submission for Target_Core_Mod/ConfigFS for
> v2.6.29. However, what would be nice if you actually sent a kernel
> patch for these issues.
I ran checkpatch on the files in drivers/lio-core ONLY. I did this by
converting all the files in drivers/lio-core through a script into a
patch, and by running checkpatch on the generated patch.
And as you already know I'm not going to work on LIO.
Bart.
next prev parent reply other threads:[~2008-12-12 7:21 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 [this message]
2008-12-12 9:40 ` Nicholas A. Bellinger
2008-12-13 6:20 ` Valdis.Kletnieks
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=e2e108260812112321w2f5b1827xe2593888e44808ae@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--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 \
/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