From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Janusz Krzysztofik <jmkrzyszt@gmail.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP1: ams-delta: Fix broken GPIO ID allocation
Date: Fri, 22 Mar 2019 15:21:34 -0700 [thread overview]
Message-ID: <20190322222134.GI19425@atomide.com> (raw)
In-Reply-To: <20190320010150.GA7872@darkstar.musicnaut.iki.fi>
* Aaro Koskinen <aaro.koskinen@iki.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@gmail.com>
> > Cc: stable@vger.kernel.org
>
> Acked-by: Aaro Koskinen <aaro.koskinen@iki.fi>
Applying into omap-for-v5.1/fixes thanks.
Tony
prev parent reply other threads:[~2019-03-22 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 20:19 [PATCH] ARM: OMAP1: ams-delta: Fix broken GPIO ID allocation Janusz Krzysztofik
2019-03-20 1:01 ` Aaro Koskinen
2019-03-22 22:21 ` Tony Lindgren [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=20190322222134.GI19425@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=jmkrzyszt@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).