diff options
| author | Johan Hovold <johan@kernel.org> | 2016-07-24 14:10:58 +0200 |
|---|---|---|
| committer | Roger Quadros <rogerq@ti.com> | 2016-08-08 11:18:40 +0300 |
| commit | 23540d6e2f3193b946c4de43e3f9654fa6d23fe7 (patch) | |
| tree | ab85deb67d734824f1d13320af668906bf8a227e /mm/mprotect.c | |
| parent | 29b4817d4018df78086157ea3a55c1d9424a7cfc (diff) | |
| download | linux-23540d6e2f3193b946c4de43e3f9654fa6d23fe7.tar.gz | |
memory: omap-gpmc: allow probe of child nodes to fail
A recent commit (inadvertently?) changed how failed probe of a gpmc
child node was handled. Instead of proceeding with setting up any other
children as before, a single error now aborts the whole process.
This change broke networking on some Overo boards due to probe failing
for an unrelated nand node. This second issue should obviously be
fixed, but let's restore the old behaviour of allowing child-node
probe to fail to avoid further similar breakage on other systems.
Fixes: d2d00862dfbb ("memory: omap-gpmc: Support general purpose input
for WAITPINs")
Cc: stable@vger.kernel.org # v4.7+
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Roger Quadros <rogerq@ti.com>
Diffstat (limited to 'mm/mprotect.c')
0 files changed, 0 insertions, 0 deletions