From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Greg Ungerer <gerg@kernel.org>
Cc: Boris Brezillon <boris.brezillon@bootlin.com>,
linux-mtd@lists.infradead.org, gerg@linux-m68k.org
Subject: Re: linux-4.17-rc4 marvell-nand.c driver problems
Date: Mon, 14 May 2018 09:33:07 +0200 [thread overview]
Message-ID: <20180514093307.48f1d26b@xps13> (raw)
In-Reply-To: <e1311707-61aa-81f0-1a37-003061560acd@kernel.org>
Hi Greg,
On Mon, 14 May 2018 09:53:26 +1000, Greg Ungerer <gerg@kernel.org>
wrote:
> Hi Boris,
>
> On 11/05/18 18:02, Boris Brezillon wrote:
> > On Fri, 11 May 2018 17:11:28 +1000
> > Greg Ungerer <gerg@kernel.org> wrote:
> >> I have a hardware platform built around the Armada 370 using NAND flash.
> >> Its old hardware, and has run pretty much every kernel version from
> >> 3.10 up to 4.16 with no problems. The flash is 128Mbyte SLC from various
> >> vendors (Spansion, Micron, etc).
> >>
> >> It has always been using the pxa3xx_nand.c driver up to now. With that
> >> gone in 4.17 I am trying out the marvell_nand.c driver. I am getting
> >> a dump just after startup:
> > > Can you try to cherry-pick this commit [1] (it should appear in
> > 4.17-rc5).
>
> That fixes the problem. Thanks for the quick response.
>
Sorry for the delay, good to know it fixed your setup, sorry for the
inconvenience.
Thanks,
Miquèl
--
Miquel Raynal, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-05-14 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 7:11 linux-4.17-rc4 marvell-nand.c driver problems Greg Ungerer
2018-05-11 8:02 ` Boris Brezillon
2018-05-11 11:26 ` Greg Ungerer
2018-05-13 23:53 ` Greg Ungerer
2018-05-14 7:33 ` Miquel Raynal [this message]
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=20180514093307.48f1d26b@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=gerg@kernel.org \
--cc=gerg@linux-m68k.org \
--cc=linux-mtd@lists.infradead.org \
/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