All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: Mike Anderson <andmike@us.ibm.com>, Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	device-mapper development <dm-devel@redhat.com>,
	Lars Marowsky-Bree <lmb@suse.de>
Subject: Re: [PATCH 2/3] sysfs representation of stacked devices (dm) (rev.2)
Date: Wed, 22 Feb 2006 12:13:56 -0500	[thread overview]
Message-ID: <43FC9BD4.1010901@ce.jp.nec.com> (raw)
In-Reply-To: <20060222163438.GC31641@agk.surrey.redhat.com>

Hi,

Alasdair G Kergon wrote:
 > This patch needs splitting up so that independent changes can be
 > considered separately.
 >
 > c.f. The proposal from Mike Anderson (repeated below) which I prefer
 > because it makes it clear that a table always belongs to exactly one md.

I like his proposed patch.
The interface is useful for my purpose too and moving table
creation inside _hash_lock means I don't need dm_get() neither.

Is it going to be pushed to upstream?
I'll remake my patch based on it.

-- 
Jun'ichi Nomura, NEC Solutions (America), Inc.

WARNING: multiple messages have this Message-ID (diff)
From: "Jun'ichi Nomura" <j-nomura@ce.jp.nec.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: Neil Brown <neilb@suse.de>, Lars Marowsky-Bree <lmb@suse.de>,
	Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	device-mapper development <dm-devel@redhat.com>,
	Mike Anderson <andmike@us.ibm.com>
Subject: Re: [PATCH 2/3] sysfs representation of stacked devices (dm) (rev.2)
Date: Wed, 22 Feb 2006 12:13:56 -0500	[thread overview]
Message-ID: <43FC9BD4.1010901@ce.jp.nec.com> (raw)
In-Reply-To: <20060222163438.GC31641@agk.surrey.redhat.com>

Hi,

Alasdair G Kergon wrote:
 > This patch needs splitting up so that independent changes can be
 > considered separately.
 >
 > c.f. The proposal from Mike Anderson (repeated below) which I prefer
 > because it makes it clear that a table always belongs to exactly one md.

I like his proposed patch.
The interface is useful for my purpose too and moving table
creation inside _hash_lock means I don't need dm_get() neither.

Is it going to be pushed to upstream?
I'll remake my patch based on it.

-- 
Jun'ichi Nomura, NEC Solutions (America), Inc.

  reply	other threads:[~2006-02-22 17:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 16:06 [PATCH 0/3] sysfs representation of stacked devices (dm/md) (rev.2) Jun'ichi Nomura
2006-02-22 16:06 ` Jun'ichi Nomura
2006-02-22 16:13 ` [PATCH 1/3] sysfs representation of stacked devices (common) (rev.2) Jun'ichi Nomura
2006-02-22 16:13   ` Jun'ichi Nomura
2006-02-22 18:48   ` Greg KH
2006-02-22 18:48     ` Greg KH
2006-02-22 22:22     ` Jun'ichi Nomura
2006-02-22 22:22       ` Jun'ichi Nomura
2006-02-22 22:28       ` Greg KH
2006-02-22 22:28         ` Greg KH
2006-02-23 19:15         ` Jun'ichi Nomura
2006-02-23 19:15           ` Jun'ichi Nomura
2006-02-24  3:40           ` Greg KH
2006-02-24  3:40             ` Greg KH
2006-02-27 16:09             ` Jun'ichi Nomura
2006-02-22 16:13 ` [PATCH 2/3] sysfs representation of stacked devices (dm) (rev.2) Jun'ichi Nomura
2006-02-22 16:13   ` Jun'ichi Nomura
2006-02-22 16:34   ` Alasdair G Kergon
2006-02-22 16:34     ` Alasdair G Kergon
2006-02-22 17:13     ` Jun'ichi Nomura [this message]
2006-02-22 17:13       ` Jun'ichi Nomura
2006-02-22 18:13       ` Alasdair G Kergon
2006-02-22 18:13         ` Alasdair G Kergon
2006-02-22 19:32         ` Jun'ichi Nomura
2006-02-22 19:32           ` Jun'ichi Nomura
2006-02-22 16:13 ` [PATCH 3/3] sysfs representation of stacked devices (md) (rev.2) Jun'ichi Nomura
2006-02-22 16:13   ` Jun'ichi Nomura
2006-02-22 18:47 ` [PATCH 0/3] sysfs representation of stacked devices (dm/md) (rev.2) Greg KH
2006-02-22 18:47   ` Greg KH

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=43FC9BD4.1010901@ce.jp.nec.com \
    --to=j-nomura@ce.jp.nec.com \
    --cc=agk@redhat.com \
    --cc=andmike@us.ibm.com \
    --cc=dm-devel@redhat.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    /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.