From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: Add and use function API for UBI
Date: Thu, 22 Sep 2016 09:49:22 +0200 [thread overview]
Message-ID: <1474530566-23625-1-git-send-email-s.hauer@pengutronix.de> (raw)
We currently use a ioctl API to manipulate UBI devices. This is
suboptimal since we have to carry code for all ioctls with us, even
when some of it may be unused. This series expands the UBI API with
calls to add/remove volumes and uses it inside the UBI commands.
The next step would be to move the commands to separate files and
to make them Kconfig configurable individually.
Sascha
----------------------------------------------------------------
Sascha Hauer (4):
mtd: ubi: Add API calls to create/remove volumes
mtd: ubi: introduce barebox specific ioctl to get ubi_num
mtd: ubi: commands: use function API to access ubi volumes
mtd: ubi: remove now unused ioctls
commands/ubi.c | 40 +++++++++++++++++++++++++++++++---------
drivers/mtd/ubi/barebox.c | 43 ++++++++++++++++++++++++++++++-------------
include/linux/mtd/ubi.h | 3 +++
include/mtd/ubi-user.h | 2 ++
4 files changed, 66 insertions(+), 22 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2016-09-22 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 7:49 Sascha Hauer [this message]
2016-09-22 7:49 ` [PATCH 1/4] mtd: ubi: Add API calls to create/remove volumes Sascha Hauer
2016-09-22 7:49 ` [PATCH 2/4] mtd: ubi: introduce barebox specific ioctl to get ubi_num Sascha Hauer
2016-09-22 7:49 ` [PATCH 3/4] mtd: ubi: commands: use function API to access ubi volumes Sascha Hauer
2016-09-22 7:49 ` [PATCH 4/4] mtd: ubi: remove now unused ioctls Sascha Hauer
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=1474530566-23625-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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