Linux Device Mapper development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Jens Axboe <jaxboe@fusionio.com>,
	LKML <linux-kernel@vger.kernel.org>,
	James Bottomley <James.Bottomley@suse.de>,
	device-mapper development <dm-devel@redhat.com>
Subject: Re: dm: improve block integrity support
Date: Fri, 15 Apr 2011 00:57:13 -0400	[thread overview]
Message-ID: <yq1wriwqfh2.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20110414144208.GA26155@redhat.com> (Mike Snitzer's message of "Thu, 14 Apr 2011 10:42:09 -0400")

>>>>> "Mike" == Mike Snitzer <snitzer@redhat.com> writes:

Mike> Martin, I've done enough testing that I am confident the DM
Mike> integrity support is in a better place with this change.  But I'd
Mike> still really appreciate it if you could verify all is well.

Still playing catchup on mail. I'll check it out and test it tomorrow...

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2011-04-15  4:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.2.00.1103290006070.2774@localhost6.localdomain6>
     [not found] ` <alpine.LFD.2.00.1103290040300.2774@localhost6.localdomain6>
     [not found]   ` <20110328230319.GA12790@redhat.com>
     [not found]     ` <4D918347.7050500@fusionio.com>
2011-03-29 13:20       ` Please revert a91a2785b20 Mike Snitzer
2011-03-29 13:35         ` James Bottomley
2011-03-29 13:42         ` Martin K. Petersen
2011-03-29 13:58           ` Need to refactor DM's integrity profile support a bit (was: Re: Please revert a91a2785b20) Mike Snitzer
2011-04-01 17:42             ` [PATCH] dm: improve block integrity support Mike Snitzer
2011-04-14 14:09               ` Mike Snitzer
2011-04-14 14:42                 ` Mike Snitzer
2011-04-15  4:57                   ` Martin K. Petersen [this message]
2011-04-05  2:09           ` Please revert a91a2785b20 NeilBrown

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=yq1wriwqfh2.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox