[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2666350.AiC22s8V5E@sven-edge>
Date: Fri, 27 Nov 2020 18:05:55 +0100
From: Sven Eckelmann <sven@...fation.org>
To: ron minnich <rminnich@...il.com>
Cc: linux-mtd@...ts.infradead.org, John Audia <graysky@...hlinux.us>,
Adrian Schmutzler <freifunk@...ianschmutzler.de>,
jstefek@...to.com,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
Richard Weinberger <richard@....at>,
Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>,
lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
Marek Vasut <marek.vasut@...il.com>,
Boris Brezillon <boris.brezillon@...labora.com>,
Ron Minnich <rminnich@...gle.com>,
Brian Norris <computersforpeace@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH] mtd: parser: cmdline: Support MTD names containing one or more colons
On Friday, 27 November 2020 17:32:02 CET ron minnich wrote:
> I'm a bit worried about how tricky this starts to get. I'm inclined to
> go back to an earlier implementation which used a character that had
> not yet been used (iirc I used [] around the PCI ID in a very early
> version). What if we used, e.g, a single ! and searched for that? It
> need not be !; pick a character. Just something not already in use, as
> the ambiguity around which ':' delimits the device has become an
> issue, as you show.
>
> Almost nothing in the original patch would change, save the character
> being searched for. By using a character we'd never used, we'd avoid
> breaking existing usage.
What? Doesn't make any sense to me. The mtdparts shown in the the commit
message is as it is. I cannot simply change it because it is in the control of
the bootloader - not the linux kernel or me. So I can also not introduce a
different character like ! for separating things.
KInd regards,
Sven
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists