All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Jonathan Corbet <corbet@lwn.net>,
	Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>, Will Drewry <wad@chromium.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	dm-devel@redhat.com, Brian Norris <briannorris@chromium.org>
Subject: [PATCH 1/5] dm: move dm_table_destroy() to same header as dm_table_create()
Date: Tue, 11 Apr 2017 17:33:40 +0200	[thread overview]
Message-ID: <20170411153344.27092-2-enric.balletbo@collabora.com> (raw)
In-Reply-To: <20170411153344.27092-1-enric.balletbo@collabora.com>

From: Brian Norris <briannorris@chromium.org>

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>
Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
---
 drivers/md/dm.h               | 1 -
 include/linux/device-mapper.h | 5 +++++
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/drivers/md/dm.h b/drivers/md/dm.h
index f298b01..c54d2f1 100644
--- a/drivers/md/dm.h
+++ b/drivers/md/dm.h
@@ -48,7 +48,6 @@ struct dm_md_mempools;
 /*-----------------------------------------------------------------
  * Internal table functions.
  *---------------------------------------------------------------*/
-void dm_table_destroy(struct dm_table *t);
 void dm_table_event_callback(struct dm_table *t,
 			     void (*fn)(void *), void *context);
 struct dm_target *dm_table_get_target(struct dm_table *t, unsigned int index);
diff --git a/include/linux/device-mapper.h b/include/linux/device-mapper.h
index a7e6903..70cb6af 100644
--- a/include/linux/device-mapper.h
+++ b/include/linux/device-mapper.h
@@ -472,6 +472,11 @@ void dm_table_set_type(struct dm_table *t, unsigned type);
 int dm_table_complete(struct dm_table *t);
 
 /*
+ * Destroy the table when finished.
+ */
+void dm_table_destroy(struct dm_table *t);
+
+/*
  * Target may require that it is never sent I/O larger than len.
  */
 int __must_check dm_set_target_max_io_len(struct dm_target *ti, sector_t len);
-- 
2.9.3

  reply	other threads:[~2017-04-11 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-11 15:33 [PATCH 0/5] dm: boot a mapped device without an initramfs Enric Balletbo i Serra
2017-04-11 15:33 ` Enric Balletbo i Serra [this message]
2017-04-11 15:33 ` [PATCH 2/5] dm: move dm definitions outside the private header to boot dm targets Enric Balletbo i Serra
2017-04-11 15:33 ` [PATCH 3/5] dm: export a table+mapped device to the ioctl interface Enric Balletbo i Serra
2017-04-11 15:33 ` [PATCH 4/5] init: add support to directly boot to a mapped device Enric Balletbo i Serra
2017-04-12  0:04   ` kbuild test robot
2017-04-11 15:33 ` [PATCH 5/5] dm verity: add support for version 0 of the on-disk format Enric Balletbo i Serra
2017-04-11 17:21   ` Milan Broz
2017-04-11 17:21     ` Milan Broz
2017-04-11 19:42     ` 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=20170411153344.27092-2-enric.balletbo@collabora.com \
    --to=enric.balletbo@collabora.com \
    --cc=agk@redhat.com \
    --cc=briannorris@chromium.org \
    --cc=corbet@lwn.net \
    --cc=dm-devel@redhat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=wad@chromium.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 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.