All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: linux-kernel@vger.kernel.org,
	device-mapper development <dm-devel@redhat.com>,
	jens.axboe@oracle.com
Subject: Re: [RESEND][PATCH] Send uevents for disk write_protect changes
Date: Tue, 21 Jul 2009 22:39:27 +0900	[thread overview]
Message-ID: <4A65C50F.6090605@kernel.org> (raw)
In-Reply-To: <200907211128.07252.knikanth@suse.de>

Nikanth Karthikesan wrote:
> Hi
> 
> This patch is needed for the dm-multipath, so that the daemon can capture the 
> event and reload the dm table when the read-only setting of the disk changes. 
> Can this be merged?

This is for the next merge window, right?

Thanks.

-- 
tejun

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: jens.axboe@oracle.com, Hannes Reinecke <hare@suse.de>,
	linux-kernel@vger.kernel.org,
	device-mapper development <dm-devel@redhat.com>
Subject: Re: [RESEND][PATCH] Send uevents for disk write_protect changes
Date: Tue, 21 Jul 2009 22:39:27 +0900	[thread overview]
Message-ID: <4A65C50F.6090605@kernel.org> (raw)
In-Reply-To: <200907211128.07252.knikanth@suse.de>

Nikanth Karthikesan wrote:
> Hi
> 
> This patch is needed for the dm-multipath, so that the daemon can capture the 
> event and reload the dm table when the read-only setting of the disk changes. 
> Can this be merged?

This is for the next merge window, right?

Thanks.

-- 
tejun

  reply	other threads:[~2009-07-21 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21  5:58 [RESEND][PATCH] Send uevents for disk write_protect changes Nikanth Karthikesan
2009-07-21 13:39 ` Tejun Heo [this message]
2009-07-21 13:39   ` Tejun Heo
2009-07-28  7:12 ` Jens Axboe

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=4A65C50F.6090605@kernel.org \
    --to=tj@kernel.org \
    --cc=dm-devel@redhat.com \
    --cc=jens.axboe@oracle.com \
    --cc=knikanth@suse.de \
    --cc=linux-kernel@vger.kernel.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.