From: Brian Norris <briannorris@chromium.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Alasdair Kergon <agk@redhat.com>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org,
Enric Balletbo i Serra <enric.balletbo@collabora.com>
Subject: Re: dm: move dm_table_destroy() to same header as dm_table_create()
Date: Tue, 4 Apr 2017 15:35:54 -0700 [thread overview]
Message-ID: <20170404223552.GA121849@google.com> (raw)
In-Reply-To: <20170328193150.GA21445@redhat.com>
On Tue, Mar 28, 2017 at 03:31:51PM -0400, Mike Snitzer wrote:
> On Tue, Mar 28 2017 at 2:31pm -0400,
> Brian Norris <briannorris@chromium.org> wrote:
>
> > If anyone is going to use dm_table_create(), they probably should be
> > able to use dm_table_destroy() too. Move the dm_table_destroy()
> > definition outside the private header, near dm_table_create()
> >
> > Signed-off-by: Brian Norris <briannorris@chromium.org>
>
> Not seeing why we need dm_table_create() exposed. So I think you went
> the wrong way with this. Unless you have an actual need, I'd prefer to
> see dm_table_create() moved from include/linux/device-mapper.h to
> drivers/md/dm.h
We've been carrying code in our ChromeOS kernel to parse a cmdline arg
for setting up early DM maps -- e.g., a dm-verity rootfs without using
an initramfs. We currently use dm_table_create() from init/*.c (and we
*should* be using dm_table_destroy() in the error paths). So I'm
certainly not going to send the patch to do the reverse :)
Enric is working on cleaning up this work to send here, so if you don't
want to see this patch now, you may well see it later.
Brian
next prev parent reply other threads:[~2017-04-04 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 18:31 [PATCH] dm: move dm_table_destroy() to same header as dm_table_create() Brian Norris
2017-03-28 19:31 ` Mike Snitzer
2017-04-04 22:35 ` Brian Norris [this message]
2017-04-05 8:04 ` Enric Balletbo i Serra
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=20170404223552.GA121849@google.com \
--to=briannorris@chromium.org \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=enric.balletbo@collabora.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