From: Joe Thornber <thornber@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, ejt@redhat.com
Subject: Re: [PATCH 1/2] dm thin: rename dm_thin_id to more generic dm_dev_id
Date: Mon, 5 Mar 2012 10:29:42 +0000 [thread overview]
Message-ID: <20120305102941.GC6431@ubuntu> (raw)
In-Reply-To: <1330732770-18621-1-git-send-email-snitzer@redhat.com>
This is part of the hsm target development work. Let's keep this in
git for now; there's no point spamming dm-devel with work in progress.
I'm happy to give you write access to my github repo if you like.
Otherwise I can merge from any git repo you wish.
On Fri, Mar 02, 2012 at 06:59:29PM -0500, Mike Snitzer wrote:
> dm_thin_id is too specific to thin devices. Rename to allow for reuse
> by other targets.
next prev parent reply other threads:[~2012-03-05 10:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 23:59 [PATCH 1/2] dm thin: rename dm_thin_id to more generic dm_dev_id Mike Snitzer
2012-03-02 23:59 ` [PATCH 2/2] dm thin: elevate the bio_prison and deferred_set code to allow for re-use Mike Snitzer
2012-03-03 0:26 ` Alasdair G Kergon
2012-03-03 3:13 ` [PATCH 2/2 v2] " Mike Snitzer
2012-03-05 10:29 ` Joe Thornber [this message]
2012-03-05 14:08 ` [PATCH 1/2] dm thin: rename dm_thin_id to more generic dm_dev_id Mike Snitzer
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=20120305102941.GC6431@ubuntu \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=ejt@redhat.com \
--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.