From: Kent Overstreet <kmo@daterainc.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dave Kleikamp <dave.kleikamp@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Maxim V. Patlasov" <mpatlasov@parallels.com>,
linux-aio@kvack.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [GIT PULL] direct IO support for loop driver
Date: Thu, 21 Nov 2013 02:13:08 -0800 [thread overview]
Message-ID: <20131121101308.GC17871@kmo-pixel> (raw)
In-Reply-To: <20131121101138.GA1100@infradead.org>
On Thu, Nov 21, 2013 at 02:11:38AM -0800, Christoph Hellwig wrote:
> On Thu, Nov 21, 2013 at 02:06:09AM -0800, Kent Overstreet wrote:
> > Can you post those patches somewhere? If that's the end goal of this
> > patch series, we should be able to look at them too.
>
> I've should have the target side back working soon as I started on it
> again about a week ago.
Broken code is fine, I just want to see the overall approach.
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
WARNING: multiple messages have this Message-ID (diff)
From: Kent Overstreet <kmo@daterainc.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Dave Kleikamp <dave.kleikamp@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Maxim V. Patlasov" <mpatlasov@parallels.com>,
linux-aio@kvack.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [GIT PULL] direct IO support for loop driver
Date: Thu, 21 Nov 2013 02:13:08 -0800 [thread overview]
Message-ID: <20131121101308.GC17871@kmo-pixel> (raw)
In-Reply-To: <20131121101138.GA1100@infradead.org>
On Thu, Nov 21, 2013 at 02:11:38AM -0800, Christoph Hellwig wrote:
> On Thu, Nov 21, 2013 at 02:06:09AM -0800, Kent Overstreet wrote:
> > Can you post those patches somewhere? If that's the end goal of this
> > patch series, we should be able to look at them too.
>
> I've should have the target side back working soon as I started on it
> again about a week ago.
Broken code is fine, I just want to see the overall approach.
next prev parent reply other threads:[~2013-11-21 10:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 19:03 [GIT PULL] direct IO support for loop driver Dave Kleikamp
2013-11-18 19:03 ` Dave Kleikamp
2013-11-18 19:07 ` Dave Kleikamp
2013-11-18 19:07 ` Dave Kleikamp
2013-11-20 21:19 ` Linus Torvalds
2013-11-20 21:19 ` Linus Torvalds
2013-11-20 21:38 ` Linus Torvalds
2013-11-20 21:38 ` Linus Torvalds
2013-11-20 21:50 ` Kent Overstreet
2013-11-20 22:46 ` Dave Kleikamp
2013-11-20 22:46 ` Dave Kleikamp
2013-11-21 4:24 ` Stephen Rothwell
2013-11-21 8:53 ` Jon Medhurst (Tixy)
2013-11-21 9:58 ` Christoph Hellwig
2013-11-21 9:58 ` Christoph Hellwig
2013-11-21 10:06 ` Kent Overstreet
2013-11-21 10:06 ` Kent Overstreet
2013-11-21 10:11 ` Christoph Hellwig
2013-11-21 10:11 ` Christoph Hellwig
2013-11-21 10:13 ` Kent Overstreet [this message]
2013-11-21 10:13 ` Kent Overstreet
2013-11-21 17:34 ` Christoph Hellwig
2013-11-21 17:34 ` Christoph Hellwig
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=20131121101308.GC17871@kmo-pixel \
--to=kmo@daterainc.com \
--cc=axboe@kernel.dk \
--cc=dave.kleikamp@oracle.com \
--cc=hch@infradead.org \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatlasov@parallels.com \
--cc=torvalds@linux-foundation.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 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.