From: Andi Kleen <andi@firstfloor.org>
To: Mike Snitzer <snitzer@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
agk@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH] Implement barrier support for single device DM devices
Date: Fri, 16 May 2008 23:48:21 +0200 [thread overview]
Message-ID: <482E0125.7070701@firstfloor.org> (raw)
In-Reply-To: <170fa0d20805161255i31d768ceh3b15c2640f06524b@mail.gmail.com>
Mike Snitzer wrote:
> Given that you feel supporting barriers on single device DM targets is
> a good thing, what is the status of such support (like Andi's patch)
> making it upstream?
It's not in 2.6.26-rc2. I was also a little surprised by it missing.
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Mike Snitzer <snitzer@gmail.com>
Cc: device-mapper development <dm-devel@redhat.com>,
agk@redhat.com, Ric Wheeler <ric@emc.com>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] Re: [PATCH] Implement barrier support for single device DM devices
Date: Fri, 16 May 2008 23:48:21 +0200 [thread overview]
Message-ID: <482E0125.7070701@firstfloor.org> (raw)
In-Reply-To: <170fa0d20805161255i31d768ceh3b15c2640f06524b@mail.gmail.com>
Mike Snitzer wrote:
> Given that you feel supporting barriers on single device DM targets is
> a good thing, what is the status of such support (like Andi's patch)
> making it upstream?
It's not in 2.6.26-rc2. I was also a little surprised by it missing.
-Andi
next prev parent reply other threads:[~2008-05-16 21:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 12:08 [PATCH] Implement barrier support for single device DM devices Andi Kleen
2008-02-15 12:20 ` Alasdair G Kergon
2008-02-15 13:07 ` Michael Tokarev
2008-02-15 14:20 ` Andi Kleen
2008-02-15 14:12 ` Alasdair G Kergon
2008-02-15 14:12 ` [dm-devel] " Alasdair G Kergon
2008-02-15 15:34 ` Andi Kleen
2008-02-15 15:34 ` [dm-devel] " Andi Kleen
2008-02-15 15:31 ` Alan Cox
2008-02-15 15:31 ` [dm-devel] " Alan Cox
2008-02-18 12:48 ` Ric Wheeler
2008-02-18 12:48 ` [dm-devel] " Ric Wheeler
2008-02-18 13:24 ` Michael Tokarev
2008-02-18 13:52 ` Ric Wheeler
2008-02-18 13:52 ` [dm-devel] " Ric Wheeler
2008-02-19 2:45 ` Alasdair G Kergon
2008-02-19 2:45 ` [dm-devel] " Alasdair G Kergon
2008-05-16 19:55 ` Mike Snitzer
2008-05-16 19:55 ` [dm-devel] " Mike Snitzer
2008-05-16 21:48 ` Andi Kleen [this message]
2008-05-16 21:48 ` Andi Kleen
2008-02-18 22:16 ` David Chinner
2008-02-19 2:56 ` Alasdair G Kergon
2008-02-19 2:56 ` [dm-devel] " Alasdair G Kergon
2008-02-19 5:36 ` David Chinner
2008-02-19 5:36 ` David Chinner
2008-02-19 9:43 ` Andi Kleen
2008-02-19 9:43 ` Andi Kleen
2008-02-19 7:19 ` Jeremy Higdon
2008-02-19 7:19 ` [dm-devel] " Jeremy Higdon
2008-02-19 7:58 ` Michael Tokarev
2008-02-20 13:38 ` Ric Wheeler
2008-02-20 13:38 ` [dm-devel] " Ric Wheeler
2008-02-21 3:29 ` Neil Brown
2008-02-21 3:29 ` [dm-devel] " Neil Brown
2008-02-21 3:39 ` Neil Brown
2008-02-17 23:31 ` David Chinner
2008-02-19 2:39 ` Alasdair G Kergon
2008-02-19 2:39 ` Alasdair G Kergon
2008-02-19 11:12 ` David Chinner
-- strict thread matches above, loose matches on Subject: below --
2008-09-11 14:12 Mat
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=482E0125.7070701@firstfloor.org \
--to=andi@firstfloor.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=snitzer@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.