lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 22 Mar 2019 15:21:34 -0700 From: Tony Lindgren <tony@...mide.com> To: Aaro Koskinen <aaro.koskinen@....fi> Cc: Janusz Krzysztofik <jmkrzyszt@...il.com>, linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, stable@...r.kernel.org Subject: Re: [PATCH] ARM: OMAP1: ams-delta: Fix broken GPIO ID allocation * Aaro Koskinen <aaro.koskinen@....fi> [190320 01:02]: > On Tue, Mar 19, 2019 at 09:19:52PM +0100, Janusz Krzysztofik wrote: > > In order to request dynamic allocationn of GPIO IDs, a negative number > > should be passed as a base GPIO ID via platform data. Unfortuntely, > > commit 771e53c4d1a1 ("ARM: OMAP1: ams-delta: Drop board specific global > > GPIO numbers") didn't follow that rule while switching to dynamically > > allocated GPIO IDs for Amstrad Delta latches, making their IDs > > overlapping with those already assigned to OMAP GPIO devices. Fix it. > > > > Fixes: 771e53c4d1a1 ("ARM: OMAP1: ams-delta: Drop board specific global GPIO numbers") > > Signed-off-by: Janusz Krzysztofik <jmkrzyszt@...il.com> > > Cc: stable@...r.kernel.org > > Acked-by: Aaro Koskinen <aaro.koskinen@....fi> Applying into omap-for-v5.1/fixes thanks. Tony
Powered by blists - more mailing lists