All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Vasily Tarasov <tarasov@vasily.name>
Cc: Joe Thornber <thornber@redhat.com>,
	Christoph Hellwig <hch@infradead.org>,
	device-mapper development <dm-devel@redhat.com>,
	Philip Shilane <philip.shilane@emc.com>,
	Sonam Mandal <sonam.dp42@gmail.com>,
	Erez Zadok <ezk@fsl.cs.sunysb.edu>
Subject: Re: [PATCH RFCv2 01/10] dm-dedup: main data structures
Date: Fri, 17 Oct 2014 13:42:51 -0400	[thread overview]
Message-ID: <20141017174251.GA25948@redhat.com> (raw)
In-Reply-To: <CAFTzLMNJ7=zc-qTcLY_BLQPRD4hiJYUAvs_AHgTgxsfg3Bb49Q@mail.gmail.com>

On Fri, Oct 17 2014 at  1:11pm -0400,
Vasily Tarasov <tarasov@vasily.name> wrote:

> Hi Mike,
> 
> Sonam Mandal, who also works on dm-dedup project, has addressed your
> comments about BUG() and BUG_ON(). She has also updated the code
> related to mark and sweep. The changes are staged here (on top of your
> dm-dedup repo):
> 
> git://git.fsl.cs.stonybrook.edu/scm/git/linux-dmdedup
> branch: dm-dedup-devel
> 
> I'm not sure if you want us to send the patches to device-mapper
> mailing list in addition to that. Let us know if we should do it.

I'll take a look next week, I need to finish up some dm-thinp work this
week.  Your repo is perfect for now.

Thanks for doing this work.
Mike

  reply	other threads:[~2014-10-17 17:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 21:56 [PATCH RFCv2 01/10] dm-dedup: main data structures Vasily Tarasov
2014-09-26 15:24 ` Mike Snitzer
2014-09-29 13:34   ` Vasily Tarasov
2014-10-17 17:11     ` Vasily Tarasov
2014-10-17 17:42       ` Mike Snitzer [this message]
2014-11-26 15:38         ` Mike Snitzer
2014-11-26 16:36           ` Erez Zadok
2014-11-26 16:47             ` Mike Snitzer
2014-11-26 18:35               ` Vasily Tarasov
2014-12-04  1:21                 ` Darrick J. Wong

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=20141017174251.GA25948@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=ezk@fsl.cs.sunysb.edu \
    --cc=hch@infradead.org \
    --cc=philip.shilane@emc.com \
    --cc=sonam.dp42@gmail.com \
    --cc=tarasov@vasily.name \
    --cc=thornber@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.