All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Re: dm snapshot: implement .iterate_devices
Date: Wed, 26 Aug 2009 20:32:02 +0100	[thread overview]
Message-ID: <20090826193202.GI643@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20090826181908.GB26018@redhat.com>

On Wed, Aug 26, 2009 at 02:19:08PM -0400, Mike Snitzer wrote:
> I'll work on a proper solution for snapshot_iterate_devices() and get
> that to you ASAP.
 
So let's push this patch as-is for 2.6.31 as it clearly fixes one problem,
and determine the right way of handling the characteristics of the 'cow'
device in a supplementary patch.

Alasdair

WARNING: multiple messages have this Message-ID (diff)
From: Alasdair G Kergon <agk@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] Re: dm snapshot: implement .iterate_devices
Date: Wed, 26 Aug 2009 20:32:02 +0100	[thread overview]
Message-ID: <20090826193202.GI643@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20090826181908.GB26018@redhat.com>

On Wed, Aug 26, 2009 at 02:19:08PM -0400, Mike Snitzer wrote:
> I'll work on a proper solution for snapshot_iterate_devices() and get
> that to you ASAP.
 
So let's push this patch as-is for 2.6.31 as it clearly fixes one problem,
and determine the right way of handling the characteristics of the 'cow'
device in a supplementary patch.

Alasdair


  reply	other threads:[~2009-08-26 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-23  6:11 [PATCH] dm snapshot: implement .iterate_devices Mike Snitzer
2009-08-24 21:15 ` Andrew Morton
2009-08-24 22:55   ` Mike Snitzer
2009-08-26 14:50 ` [PATCH] " Alasdair G Kergon
2009-08-26 14:50   ` [dm-devel] " Alasdair G Kergon
2009-08-26 18:19   ` Mike Snitzer
2009-08-26 19:32     ` Alasdair G Kergon [this message]
2009-08-26 19:32       ` [dm-devel] " Alasdair G Kergon

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=20090826193202.GI643@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@redhat.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.