From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, lvm-devel@redhat.com
Subject: Re: ANNOUNCE: remove device on close
Date: Mon, 16 Sep 2013 15:45:30 -0400 [thread overview]
Message-ID: <20130916194530.GA3513@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1309161535340.9077@file01.intranet.prod.int.rdu2.redhat.com>
On Mon, Sep 16 2013 at 3:41pm -0400,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> Hi
>
> I placed the patches for deferred removal at
> http://people.redhat.com/mpatocka/patches/kernel/deferred-remove/
Please post the kernel patch to dm-devel so it is easier for people to
review/comment. It also enables the patch to be tracked via patchwork.
Thanks,
Mike
--
lvm-devel mailing list
lvm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/lvm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: lvm-devel@redhat.com
Subject: ANNOUNCE: remove device on close
Date: Mon, 16 Sep 2013 15:45:30 -0400 [thread overview]
Message-ID: <20130916194530.GA3513@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1309161535340.9077@file01.intranet.prod.int.rdu2.redhat.com>
On Mon, Sep 16 2013 at 3:41pm -0400,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> Hi
>
> I placed the patches for deferred removal at
> http://people.redhat.com/mpatocka/patches/kernel/deferred-remove/
Please post the kernel patch to dm-devel so it is easier for people to
review/comment. It also enables the patch to be tracked via patchwork.
Thanks,
Mike
next prev parent reply other threads:[~2013-09-16 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 19:41 ANNOUNCE: remove device on close Mikulas Patocka
2013-09-16 19:41 ` Mikulas Patocka
2013-09-16 19:45 ` Mike Snitzer [this message]
2013-09-16 19:45 ` Mike Snitzer
2013-09-16 20:34 ` [PATCH] " Mikulas Patocka
2013-09-16 20:34 ` Mikulas Patocka
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=20130916194530.GA3513@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=lvm-devel@redhat.com \
--cc=mpatocka@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.