Subject: Re: [REGRESSION] linux-next panics when trying to mount root
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Richard Weinberger <richard@nod.at>,
        =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= <rafal@milecki.pl>,
        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
References: <574b1571-1664-f09f-62bf-48f7f94a51cd@axentia.se>
 <20180116143651.04bca70f@bbrezillon>
 <b5af18eb-e54d-eeab-d03b-4c0edbe74fd6@axentia.se>
 <20180116152138.18a114d6@bbrezillon>
From: Peter Rosin <peda@axentia.se>
Organization: Axentia Technologies AB
Message-ID: <6a51ff05-89ed-cd57-6d90-3af51c7ce619@axentia.se>
Date: Tue, 16 Jan 2018 16:02:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180116152138.18a114d6@bbrezillon>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Jan 2018 15:02:40.1490 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 6149b10f-294a-417d-da18-08d55cf230cc
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 4ee68585-03e1-4785-942a-df9c1871a234
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0202MB2780
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>

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...

Cheers,
Peter