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: 260 seconds]
jclsn has joined #armlinux
m5zs7k has quit [Quit: m5zs7k]
heat has quit [Ping timeout: 252 seconds]
m5zs7k has joined #armlinux
siak has joined #armlinux
amitk has joined #armlinux
Livio has joined #armlinux
monstr has joined #armlinux
Livio has quit [Ping timeout: 260 seconds]
luispm has joined #armlinux
<lag>
ukleinek: I still don't see your Ack
<lag>
pinchartl: Looks okay at first blush - will need v7 for some trivia
<lag>
Will return to reviews next week once v6.11-rc1 is out
iivanov has joined #armlinux
frieder has joined #armlinux
Livio has joined #armlinux
gclement has joined #armlinux
cbeznea has joined #armlinux
<ukleinek>
lag: that's because I didn't send it yet, will have to look first. (This was just me *expecting* to be ok after seeing the previous iteration)
<lag>
ukleinek: Okay, I am in the same boat. Will review next week.
frieder has quit [Ping timeout: 276 seconds]
frieder has joined #armlinux
frieder has quit [Ping timeout: 276 seconds]
headless has joined #armlinux
sszy has joined #armlinux
prabhakalad has joined #armlinux
tsc has quit [Quit: WeeChat 3.8]
tsc has joined #armlinux
frieder has joined #armlinux
<pinchartl>
lag: what's the trivia ? :-)
<lag>
pinchartl: You'll find out next week :)
<pinchartl>
-_-'
<lag>
pinchartl: Okay, seeing as it's you ...
<lag>
\No more reviews this week
Livio has quit [Ping timeout: 260 seconds]
<pinchartl>
lag: thank you :-)
<pinchartl>
are you on vacation this week ?
<lag>
I take a breather during the merge-window
<lag>
Catch-up on proper work!
<lag>
So vacation from upstream work, yes
headless has quit [Read error: Connection reset by peer]
iivanov has quit [Remote host closed the connection]
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
frieder has quit [Ping timeout: 276 seconds]
monstr has quit [Ping timeout: 252 seconds]
frieder has joined #armlinux
rockosov has joined #armlinux
frieder has quit [Ping timeout: 248 seconds]
Amit_T has joined #armlinux
frieder has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
frieder has quit [Ping timeout: 260 seconds]
frieder has joined #armlinux
iivanov_ has joined #armlinux
iivanov has quit [Read error: Connection reset by peer]
bjoto`` has quit [Remote host closed the connection]
bjoto has joined #armlinux
headless has joined #armlinux
monstr has joined #armlinux
<gclement>
. Durant le week-end, des groupes criminels ont cherché à tirer parti de la panne : CrowdStrike a annoncé avoir observé la diffusion d’un fichier se présentant comme un correctif, qui contenait en réalité un rançongiciel. Plusieurs faux sites usurpant l’identité de l’entreprise ont été créés durant le week-end, et cherchaient notamment à diffuser ce fichier piégé.
<gclement>
oups wrong chanel sorry ;/
psydroid2 has joined #armlinux
frieder has quit [Remote host closed the connection]
heat_ has joined #armlinux
heat has quit [Read error: Connection reset by peer]
<ukleinek>
lag: I have a device here with 4 hdd-leds and (surprise) up to 4 hdds. These leds use the disk-activity trigger. Is there a nice way to make led-1 only trigger on disk-activity on disk1? (cc: mmind00)
monstr has quit [Remote host closed the connection]
pikapika_lunar is now known as militantorc
headless has quit [Ping timeout: 260 seconds]
gclement has quit [Ping timeout: 264 seconds]
<lag>
ukleinek: My dirty little secret is that I've never developed on an LED :)
<lag>
ukleinek: I'd have to read the code, same as you
<ukleinek>
lag: ok
<ukleinek>
lag: I recently started somewhat systematic testing on a PWM driver, found quite some things to fix :-)
<mmind00>
ukleinek: I think the LED itself is probably alright as it is ... finding the trigger might be the harder part ... like I see a separate trigger for mmc0 in the avaible list of the device, but we'd need some thing about sata ;-)
<ukleinek>
mmind00: the "problem" is twofold, a) we need software support to limit a disk trigger to a certain disk, and b) how to specify that in the dts?
<cambrian_invader>
you have to do LED stuff in userspace :l
<lag>
ukleinek: You're in good hands with Heiko
<lag>
cambrian_invader: Ideally - if it's supported in sysfs
mripard has quit [Quit: mripard]
<cambrian_invader>
lag: the LED subsystem is sysfs first and devicetree second
dmart has quit [Quit: leaving]
headless has joined #armlinux
Livio has joined #armlinux
<lag>
cambrian_invader: Are you asking me, or telling me? :)
<cambrian_invader>
telling?
<cambrian_invader>
this is my observation based on my experience
<cambrian_invader>
certain things with LEDs are viewed as "userspace's responsibility" and are not available in devicetree