From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: ron minnich <rminnich@gmail.com>,
linux-mtd@lists.infradead.org,
Vignesh Raghavendra <vigneshr@ti.com>,
Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH 1/1] mtd/intel-spi: Support cmdline-based partition
Date: Fri, 27 Mar 2020 18:48:02 +0200 [thread overview]
Message-ID: <20200327164802.GN2564@lahna.fi.intel.com> (raw)
In-Reply-To: <20200327171907.7a7ffc73@xps13>
On Fri, Mar 27, 2020 at 05:19:07PM +0100, Miquel Raynal wrote:
> Hi Mika,
>
> Mika Westerberg <mika.westerberg@linux.intel.com> wrote on Fri, 27 Mar
> 2020 17:56:08 +0200:
>
> > Hi,
> >
> > I don't think it is good idea to change PCI device name like that.
> >
> > Instead the MTD cmdline parser should be teach to handle names like this
> > properly.
>
> It is a bit more complicated than that since parsers have been using
> this syntax for a long time and, more importantly, it means
> potentially updating all bootloaders.
>
> I am not against updating the parser, but the s/:/|/ solution proposed
> before is rather undescriptive and it is hard to find an alternative
> character that would have a meaning here.
I'm completely unfamiliar with these but would escape char work here? I
mean if you want ":" to be parsed literally then you pass "\:" in the
command line. That should work with the existing and also allow
supporting SPI NOR controllers on PCI bus.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-03-27 16:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 19:58 [PATCH 1/1] mtd/intel-spi: Support cmdline-based partition ron minnich
2020-03-23 23:19 ` ron minnich
2020-03-25 17:34 ` ron minnich
2020-03-25 17:34 ` ron minnich
2020-03-27 15:48 ` ron minnich
2020-03-27 15:56 ` Mika Westerberg
2020-03-27 16:19 ` Miquel Raynal
2020-03-27 16:48 ` Mika Westerberg [this message]
2020-03-27 16:52 ` Miquel Raynal
2020-03-27 17:05 ` ron minnich
2020-03-27 17:16 ` Mika Westerberg
2020-03-27 17:39 ` ron minnich
2020-03-27 23:53 ` ron minnich
2020-03-30 6:08 ` Mika Westerberg
2020-03-30 7:27 ` Miquel Raynal
2020-03-30 15:53 ` ron minnich
2020-04-01 7:41 ` Miquel Raynal
2020-04-01 15:42 ` ron minnich
2020-04-01 19:49 ` ron minnich
2020-04-27 9:16 ` Boris Brezillon
2020-04-27 9:49 ` Boris Brezillon
2020-04-27 14:41 ` Miquel Raynal
2020-04-27 18:48 ` ron minnich
2020-04-27 18:50 ` ron minnich
2020-04-27 18:56 ` Miquel Raynal
2020-04-27 18:59 ` ron minnich
2020-04-27 19:21 ` Boris Brezillon
2020-04-27 19:31 ` ron minnich
2020-04-27 20:31 ` ron minnich
2020-04-27 21:20 ` Miquel Raynal
2020-03-27 16:53 ` ron minnich
2020-03-27 16:15 ` 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=20200327164802.GN2564@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=rminnich@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.