From: Richard Weinberger <richard@nod.at>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Tudor Ambarus <Tudor.Ambarus@microchip.com>
Subject: Re: [PATCH v2] mtd: implement proper partition handling
Date: Thu, 9 Jan 2020 19:43:04 +0100 (CET) [thread overview]
Message-ID: <1737779363.17836.1578595384783.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <20200109191304.636c82e7@xps13>
Miquel,
----- Ursprüngliche Mail -----
>> What problem does this solve?
>> ...beside of a nice diffstat which removes more than it adds. :-)
>
> It is much easier to escalade to the top most "master" device when
> there are multiple levels of partitioning, which was not cleanly
> described IMHO. Also it is already used in the MLC-in-pseudo-SLC-mode
> series :)
Ok. In fact I "found" this patch my looking at the SLC emulation patches.
>> > +static inline struct mtd_info *mtd_get_master(struct mtd_info *mtd)
>> > +{
>> > + while (mtd->parent)
>> > + mtd = mtd->parent;
>> > +
>> > + return mtd;
>> > +}
>>
>> So, parent == master?
>
> top most parent (the one without parent) == master !
>
>>
>> When I create a MTD ontop of UBI using gluebi, who will be parent/master?
>
> I don't really understand the issue here?
Let's say I have mtd0 with an ubi and a volume "xxx". After enabling
gluebi a new mtd1 will arrive on the system.
The stacking is mtd0 -> ubi (volume xxx) -> mtd1.
Is now a relationship between mtd1 and mtd0?
I'd expect mtd1's parent being mtd0.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-01-09 18:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 11:19 [PATCH v2] mtd: implement proper partition handling Miquel Raynal
2020-01-08 23:34 ` Richard Weinberger
2020-01-09 18:13 ` Miquel Raynal
2020-01-09 18:43 ` Richard Weinberger [this message]
2020-01-09 18:45 ` Miquel Raynal
2020-01-09 19:13 ` Boris Brezillon
2020-01-09 19:23 ` Miquel Raynal
2020-01-09 19:37 ` Boris Brezillon
2020-01-10 8:28 ` Miquel Raynal
2020-01-10 9:46 ` Boris Brezillon
2020-01-10 9:55 ` Miquel Raynal
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=1737779363.17836.1578595384783.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=Tudor.Ambarus@microchip.com \
--cc=boris.brezillon@collabora.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vigneshr@ti.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