All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Tomohiro Kusumi <kusumi.tomohiro@jp.fujitsu.com>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org,
	Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: [PATCH] fix hard-coded disk header chunk size for persistent snapshot
Date: Wed, 12 May 2010 02:39:09 +0100	[thread overview]
Message-ID: <20100512013909.GD2377@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4BEA0472.1060300@jp.fujitsu.com>

On Wed, May 12, 2010 at 10:29:22AM +0900, Tomohiro Kusumi wrote:
> This patch fixes hard-coded value for the size of a chunk that includes
> disk header for persistent snapshot. It should be changed to existing
> macro NUM_SNAPSHOT_HDR_CHUNKS instead of using hard-coded value 1.
 
Any more places too?  (E.g. persistent_commit_merge)

Alasdair

  reply	other threads:[~2010-05-12  1:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12  1:29 [PATCH] fix hard-coded disk header chunk size for persistent snapshot Tomohiro Kusumi
2010-05-12  1:39 ` Alasdair G Kergon [this message]
2010-05-12  4:58   ` Mikulas Patocka
2010-05-12  5:57     ` Tomohiro Kusumi

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=20100512013909.GD2377@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=kusumi.tomohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.