ChanServ changed the topic of #linux-msm to:
Caterpillar has quit [Ping timeout: 480 seconds]
Caterpillar has joined #linux-msm
Daanct12 has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
jmassot has joined #linux-msm
Caterpillar has quit [Ping timeout: 480 seconds]
Caterpillar has joined #linux-msm
pespin has joined #linux-msm
Caterpillar has quit [Ping timeout: 480 seconds]
Daanct12 has quit [Quit: WeeChat 4.1.2]
f_ has quit [Ping timeout: 480 seconds]
Caterpillar has joined #linux-msm
f_ has joined #linux-msm
<bamse> arnd: forgot to check with you as well...i merged the pull requests into my 6.8 branches, so they will come there...but you're right i should double check to see if anything should be picked for 6.7
<minecrell> bamse: Can you check why https://patchwork.kernel.org/project/linux-arm-msm/patch/20231004-clk-qcom-smd-rpm-unused-v2-1-9a5281f324dc@kernkonzept.com/ is marked as "Changes Requested"? At least for Konrad's comment we agreed at the end that it is fine as-is
jhovold has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Ping timeout: 480 seconds]
mripard has quit [Quit: mripard]
djakov has joined #linux-msm
djakov_ has quit [Read error: Connection reset by peer]
<calebccff> minecrell: lumag: im confused about the PMIC GPIOs on db410c. The schematics number them starting from 1, and it looks like this was blindly copied to the DTS, it has two LEDs connected to pm8916_gpios "1" and "2", but in the kernel indexing starts from 0 right?
<calebccff> the u-boot DTS uses 0-based indexing for them
<calebccff> I ask because the third GPIO is the USB hub reset pin
<lumag> let me check...