From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Quentin Schulz <quentin.schulz@bootlin.com>
Cc: dedekind1@gmail.com, richard@nod.at, dwmw2@infradead.org,
computersforpeace@gmail.com, marek.vasut@gmail.com,
linux-mtd@lists.infradead.org, thomas.petazzoni@bootlin.com,
david.oberhollenzer@sigma-star.at
Subject: Re: [PATCH v2 2/4] libubi: add volume flags to ubi_mkvol_request
Date: Thu, 28 Jun 2018 09:50:40 +0200 [thread overview]
Message-ID: <20180628095040.1c1b1ea2@bbrezillon> (raw)
In-Reply-To: <20180628074344.10249-3-quentin.schulz@bootlin.com>
On Thu, 28 Jun 2018 09:43:42 +0200
Quentin Schulz <quentin.schulz@bootlin.com> wrote:
> Now that we have per-UBI volume flags (for instance for skipping CRC
> check when opening it) from the Linux header, let's add it to the
> ubi_mkvol_request in libubi and assign the flags to ubi_mkvol_req from
> the Linux header from ubi_mkvol.
>
> Suggested-by: Boris Brezillon <boris.brezillon@bootlin.com>
> Signed-off-by: Quentin Schulz <quentin.schulz@bootlin.com>
Reviewed-by: Boris Brezillon <boris.brezillon@bootlin.com>
> ---
> include/libubi.h | 2 ++
> lib/libubi.c | 1 +
> 2 files changed, 3 insertions(+)
>
> diff --git a/include/libubi.h b/include/libubi.h
> index 4d6a7ee..46596a3 100644
> --- a/include/libubi.h
> +++ b/include/libubi.h
> @@ -69,6 +69,7 @@ struct ubi_attach_request
> * @bytes: volume size in bytes
> * @vol_type: volume type (%UBI_DYNAMIC_VOLUME or %UBI_STATIC_VOLUME)
> * @name: volume name
> + * @flags: volume flags
> */
> struct ubi_mkvol_request
> {
> @@ -77,6 +78,7 @@ struct ubi_mkvol_request
> long long bytes;
> int vol_type;
> const char *name;
> + uint8_t flags;
> };
>
> /**
> diff --git a/lib/libubi.c b/lib/libubi.c
> index 978b433..4322a19 100644
> --- a/lib/libubi.c
> +++ b/lib/libubi.c
> @@ -1000,6 +1000,7 @@ int ubi_mkvol(libubi_t desc, const char *node, struct ubi_mkvol_request *req)
> r.alignment = req->alignment;
> r.bytes = req->bytes;
> r.vol_type = req->vol_type;
> + r.flags = req->flags;
>
> n = strlen(req->name);
> if (n > UBI_MAX_VOLUME_NAME)
next prev parent reply other threads:[~2018-06-28 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 7:43 [PATCH v2 0/4] ubi-utils: add possibility to flag a static volume to skip CRC check when opening Quentin Schulz
2018-06-28 7:43 ` [PATCH v2 1/4] UBI: update ubi-user.h and ubi-media.h Quentin Schulz
2018-06-28 7:50 ` Boris Brezillon
2018-06-28 7:43 ` [PATCH v2 2/4] libubi: add volume flags to ubi_mkvol_request Quentin Schulz
2018-06-28 7:50 ` Boris Brezillon [this message]
2018-06-28 7:43 ` [PATCH v2 3/4] ubi-utils: ubimkvol: add support for skipping CRC check of a static volume when opening Quentin Schulz
2018-06-28 7:50 ` Boris Brezillon
2018-06-28 7:43 ` [PATCH v2 4/4] ubi-utils: ubinize: " Quentin Schulz
2018-06-28 7:50 ` Boris Brezillon
2018-06-28 11:48 ` [PATCH v2 0/4] ubi-utils: add possibility to flag a static volume to skip CRC check " David Oberhollenzer
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=20180628095040.1c1b1ea2@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=david.oberhollenzer@sigma-star.at \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=quentin.schulz@bootlin.com \
--cc=richard@nod.at \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).