[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160803080149.GB15860@localhost>
Date: Wed, 3 Aug 2016 10:01:49 +0200
From: Johan Hovold <johan@...nel.org>
To: Roger Quadros <rogerq@...com>
Cc: Tony Lindgren <tony@...mide.com>, Johan Hovold <johan@...nel.org>,
BenoƮt Cousson <bcousson@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@...linux.org.uk>,
linux-omap@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH 0/3] ARM: omap: fix 4.7 gpmc networking regression
On Wed, Aug 03, 2016 at 10:46:24AM +0300, Roger Quadros wrote:
> On 02/08/16 13:35, Tony Lindgren wrote:
> > * Johan Hovold <johan@...nel.org> [160724 05:11]:
> >> Networking is currently broken for Overo boards due to a regression in
> >> 4.7. I bisected it down to
> >>
> >> d2d00862dfbb ("memory: omap-gpmc: Support general purpose input
> >> for WAITPINs")
> > ...
> >
> >> Note that simply fixing the Overo NAND issue would fix the Overo
> >> networking regression, but by restoring the 4.6 gpmc-probe behaviour
> >> similar regressions on other OMAP systems are also avoided.
> >
> > Roger, got a better fix in mind?
> >
>
> Nope. I'll take patch 1 in my omap-gpmc queue for v4.8.
> Thanks for the fixes Johan.
Now that 4.7 has been released, you may want to consider adding a stable
tag also for the first patch to avoid similar issues on other systems
when they get updated to 4.7-stable.
Thanks,
Johan
Powered by blists - more mailing lists