Linux Device Mapper development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>,
	Thomas Jaskiewicz <tomj@permabit.com>
Subject: Re: dm-bufio: move dm-bufio.h to include/linux/
Date: Mon, 12 Mar 2018 00:48:27 -0700	[thread overview]
Message-ID: <20180312074827.GA30695@infradead.org> (raw)
In-Reply-To: <20180308203621.GA8133@redhat.com>

On Thu, Mar 08, 2018 at 03:36:21PM -0500, Mike Snitzer wrote:
> While I appreciate your interest in what constitutes a reasonable change
> for DM, why are you so emphatic about disallowing out-of-tree DM modules
> from using dm-bufio?

Because I'd rather get them into the tree than providing escapes just
for them. 

  reply	other threads:[~2018-03-12  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08  9:22 [PATCH] dm-bufio: move dm-bufio.h to include/linux/ Mikulas Patocka
2018-03-08 14:49 ` Christoph Hellwig
2018-03-08 20:36   ` Mike Snitzer
2018-03-12  7:48     ` Christoph Hellwig [this message]
2018-03-12 15:57       ` Mike Snitzer
2018-03-09  3:56   ` [PATCH] " Mikulas Patocka

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=20180312074827.GA30695@infradead.org \
    --to=hch@infradead.org \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@redhat.com \
    --cc=snitzer@redhat.com \
    --cc=tomj@permabit.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