ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
jclsn has quit [Ping timeout: 272 seconds]
jclsn has joined #armlinux
apritzel has quit [Ping timeout: 276 seconds]
nsaenz has joined #armlinux
nsaenz has quit [Ping timeout: 272 seconds]
System_Error has quit [Remote host closed the connection]
haritz has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
haritz has joined #armlinux
haritz has joined #armlinux
haritz has quit [Changing host]
System_Error has joined #armlinux
CrashTestDummy has joined #armlinux
CrashTestDummy has quit [Client Quit]
siak has joined #armlinux
nsaenz has joined #armlinux
nsaenz has quit [Ping timeout: 268 seconds]
siak has quit [Remote host closed the connection]
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
monstr has joined #armlinux
sszy has joined #armlinux
monstr has quit [Ping timeout: 252 seconds]
haritz has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
apritzel has joined #armlinux
nsaenz has joined #armlinux
apritzel has quit [Ping timeout: 252 seconds]
monstr has joined #armlinux
mripard has joined #armlinux
frieder has joined #armlinux
atorgue__ has joined #armlinux
atorgue has joined #armlinux
atorgue1 has quit [Read error: Connection reset by peer]
atorgue__ has quit [Read error: Connection reset by peer]
graham_north has joined #armlinux
rvalue- has joined #armlinux
rvalue has quit [Ping timeout: 276 seconds]
cbeznea has joined #armlinux
rvalue- is now known as rvalue
headless has joined #armlinux
frieder has quit [Ping timeout: 276 seconds]
Xogium has quit [Ping timeout: 252 seconds]
frieder has joined #armlinux
Xogium has joined #armlinux
atorgue1 has joined #armlinux
atorgue__ has joined #armlinux
atorgue has quit [Read error: Connection reset by peer]
Xogium has quit [Remote host closed the connection]
Xogium has joined #armlinux
atorgue1 has quit [Read error: Connection reset by peer]
Xogium has quit [Remote host closed the connection]
atorgue1 has joined #armlinux
atorgue__ has quit [Read error: Connection reset by peer]
atorgue__ has joined #armlinux
atorgue1 has quit [Read error: Connection reset by peer]
Xogium has joined #armlinux
prabhakalad has quit [Ping timeout: 252 seconds]
prabhakalad has joined #armlinux
gclement has joined #armlinux
Xogium has quit [Remote host closed the connection]
Xogium has joined #armlinux
Xogium has quit [Remote host closed the connection]
<krzk>
ukleinek: hey, I don't know when was it merged/accepted etc, but from stable kernel rules this feels ok. Binding was incomplete, driver as well.
<krzk>
ukleinek: so whether backporting makes much sense etc - I don't know - but this looks like a bugfix, thus stable is ok
<ukleinek>
krzk: it wasn't merged/accepted yet. I wonder if I should drop the Cc on accepting
<robmur01>
FWIW it's not uncommon to run LTS kernels on new platforms, which may correspondingly use the new binding - I guess strictly it's still fair to say that 6.12 only supports the certain hardware configurations that 6.12 supports, but IMO it seems a bit harsh for such a relatively minor change
monstr has quit [Ping timeout: 252 seconds]
<robmur01>
especially in the case where there *is* a driver which will still probe the new binding without error but just not work properly - that's very different from no driver from the user's perspective
<krzk>
ukleinek: then it is confusing... it is cc-stable of something which is not in stable? This makes on sense at all
<ukleinek>
krzk: with my pwm maintainer hat on I have to decide if I keep or drop the Cc: stable line
<krzk>
ukleinek: but fixes commit points to 2024, so how could this be not merged?
<ukleinek>
krzk: ah, you talked about the commit to fix, I talked about the fix.
<krzk>
ukleinek: then I miss the point. I understood that original commit had incomplete hardware description up to the point it was buggy, thus Fixes and CC-stable.
<krzk>
It is not the case? then what is the case here?
<ukleinek>
krzk: my train of thought was: If a machine runs 6.12 today it uses the old binding anyhow and so works fine. And that 6.12 doesn't work with the new/fixed binding is ok?
<ukleinek>
(FTR: This became somewhat moot, I already accepted the patch and kept the Cc: stable line)
<krzk>
ukleinek: well, put like that backport is not correct, but: driver change was kept backwards compatible, so no existing users will degrade, and I imagine there was some user of the binding which was not working because of missing hardware description
<krzk>
so the question is whether that 6.12 was working fine or not
<ukleinek>
If I understand correctly it worked in practise because the axi clock is always-on
apritzel has quit [Ping timeout: 276 seconds]
HerbY_NL has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
System_Error has quit [Remote host closed the connection]
hanetzer has joined #armlinux
System_Error has joined #armlinux
HerbY_NL has joined #armlinux
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
apritzel has joined #armlinux
HerbY_NL has quit [Quit: My Mac has gone to sleep. ZZZzzz…]