From: "Rafał Miłecki" <rafal@milecki.pl>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Peter Rosin <peda@axentia.se>,
Richard Weinberger <richard@nod.at>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] linux-next panics when trying to mount root
Date: Wed, 17 Jan 2018 09:20:11 +0100 [thread overview]
Message-ID: <0d3201d921386c32d2b65b3b7d3e10e7@milecki.pl> (raw)
In-Reply-To: <20180116163032.54a392c7@bbrezillon>
On 2018-01-16 16:30, Boris Brezillon wrote:
> On Tue, 16 Jan 2018 16:02:35 +0100
> Peter Rosin <peda@axentia.se> wrote:
>
>> On 2018-01-16 15:21, Boris Brezillon wrote:
>> > On Tue, 16 Jan 2018 14:56:52 +0100
>> > Peter Rosin <peda@axentia.se> wrote:
>> >
>> >> Hmmm, I guess the question is if the command line should override the
>> >> device tree or not?
>> >
>> > Yep, that's the problem. Now the core parses the compatible to decides
>> > which part parser should be used. The thing is, the "cmdline" parser is
>> > not yet exposing a compatible id, and even if it was, this would
>> > require patching all DTs to add this new compatible.
>> >
>> > partitions {
>> > compatible = "cmdline", "fixed-partitions";
>> > ...
>> > };
>> >
>> > Not really an option, so I'll drop the 2 patches for now until we find a
>> > better solution.
>> >
>> >> I'm going to send a patch for the above dts change either way...
>> >
>> > If you want, but that does not solve the problem: we should not break
>> > existing users.
>>
>> Well, don't let these devices stop you, they will not get a new kernel
>> w/o also getting a new dtb, and I can handle this just fine. But maybe
>> I'm just the first reporter and you'd rather not risk anything?
>> Anyway,
>> just wanted to let you know where I stand...
>
> Unfortunately, at91 is not the only platform to have "fixed-partitions"
> defined in its DTs, and I guess users of other platforms also like to
> override the default MTD layout by their own using mtdparts.I'd like to
> find a solution that keeps everyone happy.
I absolutely agree with Boris, we can't risk such regressions. That had
to
be dropped and I'm looking for a better solution.
next prev parent reply other threads:[~2018-01-17 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 13:28 Peter Rosin
2018-01-16 13:36 ` Boris Brezillon
2018-01-16 13:56 ` Peter Rosin
2018-01-16 14:21 ` Boris Brezillon
2018-01-16 15:02 ` Peter Rosin
2018-01-16 15:30 ` Boris Brezillon
2018-01-17 8:20 ` Rafał Miłecki [this message]
2018-01-17 8:27 ` Rafał Miłecki
2018-01-17 9:27 ` Peter Rosin
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=0d3201d921386c32d2b65b3b7d3e10e7@milecki.pl \
--to=rafal@milecki.pl \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=peda@axentia.se \
--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
all inboxes | Powered by JetHome®