linux-kernel - Re: [PATCH] clk: at91: fix at91sam9x5 peripheral clock number

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 20 Feb 2019 11:39:48 -0800
From:   Stephen Boyd <sboyd@...nel.org>
To:     Nicolas.Ferre@...rochip.com, alexandre.belloni@...tlin.com
Cc:     mturquette@...libre.com, linux-clk@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] clk: at91: fix at91sam9x5 peripheral clock number

Quoting Nicolas.Ferre@...rochip.com (2019-02-20 03:18:40)
> On 19/02/2019 at 17:51, Alexandre Belloni wrote:
> > nck() looks at the last id in an array and unfortunately,
> > at91sam9x35_periphck has a sentinel, hence the id is 0 and the calculated
> > number of peripheral clocks is 1 instead of a maximum of 31.
> > 
> > Fixes: 1eabdc2f9dd8 ("clk: at91: add at91sam9x5 PMCs driver")
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@...tlin.com>
> 
> Acked-by: Nicolas Ferre <nicolas.ferre@...rochip.com>
> Cc: <stable@...r.kernel.org> # v4.20+
> 
> It would be nice to queue it as a fix the soonest, as it impacts 5.0 but 
> not 4.20 due to a switch from one DT binding to another (read: a real 
> regression)... But I know it's a bit late in the cycle...
> 

Ok. Let's send it off tomorrow.