linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "shli@kernel.org" <shli@kernel.org>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: md: rename some drivers/md/ files to have an "md-" prefix
Date: Tue, 10 Oct 2017 20:01:02 -0400	[thread overview]
Message-ID: <20171011000102.GB15061@redhat.com> (raw)
In-Reply-To: <1507670992.2815.59.camel@wdc.com>

On Tue, Oct 10 2017 at  5:29pm -0400,
Bart Van Assche <Bart.VanAssche@wdc.com> wrote:

> On Tue, 2017-10-10 at 17:02 -0400, Mike Snitzer wrote:
> > Motivated by the desire to illiminate the imprecise nature of
> > DM-specific patches being unnecessarily sent to both the MD maintainer
> > and mailing-list.  Which is born out of the fact that DM files also
> > reside in drivers/md/
> > 
> > Now all MD-specific files in drivers/md/ start with either "raid" or
> > "md-" and the MAINTAINERS file has been updated accordingly.
> 
> Hello Mike,
> 
> Although this patch looks fine to me: has it been considered to move the
> device mapper files into a new subdirectory, e.g. drivers/dm?

I did think about it briefly.  But there is some sharing between DM and
MD (due to dm-raid.c) -- so I figured it easiest to leave well enough
alone.

This patch will be perfectly fine so long as we just add the appropriate
prefixes to new DM and MD source files.

Mike

      reply	other threads:[~2017-10-11  0:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 21:02 [PATCH] md: rename some drivers/md/ files to have an "md-" prefix Mike Snitzer
2017-10-10 21:29 ` Shaohua Li
2017-10-10 23:55   ` Mike Snitzer
2017-10-11  1:49     ` Shaohua Li
2017-10-11 19:53     ` Shaohua Li
2017-10-11 20:17       ` Mike Snitzer
2017-10-10 21:29 ` [dm-devel] [PATCH] " Bart Van Assche
2017-10-11  0:01   ` Mike Snitzer [this message]

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=20171011000102.GB15061@redhat.com \
    --to=snitzer@redhat.com \
    --cc=Bart.VanAssche@wdc.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=shli@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).