public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Richard Weinberger <richard@nod.at>,
	Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH RFC 1/2] ubi: add flags1 field to the EC header
Date: Fri, 30 Dec 2016 18:11:50 +0100	[thread overview]
Message-ID: <20161230171151.13448-1-zajec5@gmail.com> (raw)

From: Rafał Miłecki <rafal@milecki.pl>

It allows storing extra information about header or a whole PEB.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
 drivers/mtd/ubi/ubi-media.h | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/mtd/ubi/ubi-media.h b/drivers/mtd/ubi/ubi-media.h
index 22ed3f6..58065ef 100644
--- a/drivers/mtd/ubi/ubi-media.h
+++ b/drivers/mtd/ubi/ubi-media.h
@@ -125,6 +125,7 @@ enum {
  * @magic: erase counter header magic number (%UBI_EC_HDR_MAGIC)
  * @version: version of UBI implementation which is supposed to accept this
  *           UBI image
+ * @flags1: flags describing header/block
  * @padding1: reserved for future, zeroes
  * @ec: the erase counter
  * @vid_hdr_offset: where the VID header starts
@@ -157,7 +158,8 @@ enum {
 struct ubi_ec_hdr {
 	__be32  magic;
 	__u8    version;
-	__u8    padding1[3];
+	__u8	flags1;
+	__u8    padding1[2];
 	__be64  ec; /* Warning: the current limit is 31-bit anyway! */
 	__be32  vid_hdr_offset;
 	__be32  data_offset;
-- 
2.10.1

             reply	other threads:[~2016-12-30 17:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-30 17:11 Rafał Miłecki [this message]
2016-12-30 17:11 ` [PATCH RFC 2/2] ubi: add support for UBI_EC_FLAG_ERASE_FROM_HERE Rafał Miłecki
2016-12-30 20:47   ` Richard Weinberger
2016-12-30 21:44     ` Rafał Miłecki
2016-12-31 10:03       ` Richard Weinberger
2016-12-31  9:37     ` Boris Brezillon

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=20161230171151.13448-1-zajec5@gmail.com \
    --to=zajec5@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rafal@milecki.pl \
    --cc=richard@nod.at \
    /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