[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200109182807.04c8866a@xps13>
Date: Thu, 9 Jan 2020 18:28:07 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Kamal Dasu <kamal.dasu@...adcom.com>
Cc: Richard Weinberger <richard@....at>,
Kamal Dasu <kdasu.kdev@...il.com>,
linux-mtd <linux-mtd@...ts.infradead.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
Marek Vasut <marek.vasut@...il.com>,
Vignesh Raghavendra <vigneshr@...com>
Subject: Re: [PATCH] mtd: set mtd partition panic write flag
Hi Kamal,
Kamal Dasu <kamal.dasu@...adcom.com> wrote on Thu, 9 Jan 2020 10:25:59
-0500:
> Miquel,
>
> Yes the issue is still open. I was trying to understand the suggestion
> and did not get a reply on the question I had
>
> Richard wrote :
> "So the right fix would be setting the parent's oops_panic_write in
> mtd_panic_write().
> Then we don't have to touch mtdpart.c"
>
> How do I get access to the parts parent in the core ?. Maybe I am
> missing something.
I think the solution is to set the oops_panic_write of the root parent, instead of updating the flag of the mtd device itself (which is maybe a partition).
Would this help?
https://www.spinics.net/lists/linux-mtd/msg10454.html
Thanks,
Miquèl
Powered by blists - more mailing lists