Thursday, 2026-08-20

*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has quit IRC (Read error: Connection reset by peer)00:33
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has joined #cip00:34
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has quit IRC (Read error: Connection reset by peer)00:35
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has joined #cip00:40
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has quit IRC (Read error: Connection reset by peer)00:40
*** vigneshr <vigneshr!uid375618@user/vigneshr> has quit IRC (Quit: Connection closed for inactivity)01:56
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has quit IRC (Quit: Coyote finally caught me)04:40
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has joined #cip04:56
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has joined #cip04:58
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has quit IRC (Client Quit)04:58
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has joined #cip04:59
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has quit IRC (Client Quit)05:01
*** iwamatsu <iwamatsu!~iwamatsu@www1015ue.sakura.ne.jp> has joined #cip05:02
*** iwamatsu__ <iwamatsu__!~iwamatsu_@h216015.dynamic.ppp.asahi-net.or.jp> has joined #cip05:04
*** iwamatsu__ <iwamatsu__!~iwamatsu_@h216015.dynamic.ppp.asahi-net.or.jp> has quit IRC (Client Quit)05:04
*** iwamatsu85 <iwamatsu85!~iwamatsu@user/iwamatsu> has joined #cip05:15
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:50
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Remote host closed the connection)05:51
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip05:53
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Remote host closed the connection)06:10
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)06:14
*** frieder <frieder!~frieder@88.130.219.91> has joined #cip06:29
*** tmerciai <tmerciai!~tmerciai@188.217.33.217> has joined #cip07:05
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has quit IRC (Ping timeout: 252 seconds)07:06
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has joined #cip07:08
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has quit IRC (Client Quit)07:13
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has joined #cip07:13
*** tmerciai <tmerciai!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 253 seconds)07:15
*** tmerciai <tmerciai!~tmerciai@188.217.33.217> has joined #cip07:16
*** sskartheekadivi <sskartheekadivi!~sskarthee@user/sskartheekadivi> has quit IRC (Ping timeout: 269 seconds)07:27
*** sskartheekadivi <sskartheekadivi!~sskarthee@user/sskartheekadivi> has joined #cip07:28
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip07:42
*** tmerciai <tmerciai!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 256 seconds)07:45
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has joined #cip08:08
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 247 seconds)08:10
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip08:14
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 241 seconds)08:17
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has joined #cip09:03
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 244 seconds)09:05
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip09:13
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip09:14
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 259 seconds)09:15
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has joined #cip09:22
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 261 seconds)09:25
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip09:26
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has quit IRC (Remote host closed the connection)09:27
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has joined #cip09:29
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 252 seconds)09:31
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip09:41
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 271 seconds)09:44
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has joined #cip09:53
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 262 seconds)09:56
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)10:02
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip10:19
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 246 seconds)10:22
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Remote host closed the connection)10:54
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip10:54
*** noctux <noctux!~noctux@user/noctux> has quit IRC (Ping timeout: 264 seconds)11:01
*** noctux <noctux!~noctux@user/noctux> has joined #cip11:02
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has quit IRC (Read error: Connection reset by peer)11:29
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has joined #cip11:39
*** jki <jki!~jki@46.128.82.95> has joined #cip11:56
jkihi everyone11:59
pave1hi!11:59
ulihello11:59
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has joined #cip12:00
jkilet's start the show12:00
jki#startmeeting CIP IRC weekly meeting12:00
collab-meetbotMeeting started Thu Aug 20 12:00:55 2026 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:00
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:00
jki#topic AI review12:01
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:01
jkinothing on the list - but I notice that there if a namespace collision now :D12:01
jki"AI review"...12:01
jkianyway12:01
uli:)12:01
jki512:01
jki412:01
jki312:01
jki212:02
jki112:02
jki#topic Kernel maintenance updates12:02
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:02
ulii pushed 4.412:02
pave1AI should really be called "LLM".12:02
pave1I did reviews, 6.12.103 and 104.12:02
masamiThis week reported 854 new CVEs and 43 updated CVEs.12:02
jkinormal numbers again, nice12:02
iwamatsu85hello12:03
iwamatsu85I did not work on this week.12:04
iwamatsu85beacause I was on vacation.12:04
*** iwamatsu85 is now known as iwamatsu__12:05
jkihope you enjoyed12:05
iwamatsu__:-)12:05
jkianything else to add?12:05
jki512:05
jki412:06
jki312:06
jki212:06
jki112:06
jki#topic Kernel release status12:06
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:06
jki6.1-rt was late - when I looked12:06
pave1rt did suitable 6.1-rt, so ... I was lucky this time.12:06
jkinow we are fine12:06
jkiperfect12:06
jkinext to release would be 6.1212:06
jkianything else on this?12:07
pave1and I guess 4.4-rt.12:07
pave1No need to wait when -cip is available.12:07
jki4.4-rt is only due in september12:07
jkiis it out of sync?12:08
pave1aha, my notes say Aug 30, I'll double check.12:08
pave1sorry, likely my mistake.12:08
jkiall fine12:08
jkithen let's move on12:09
jki512:09
jki412:09
jki312:09
jki212:09
jki112:09
jki#topic Kernel testing12:09
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:09
patersoncHello12:09
patersoncThe Ti LAVA lab is currently offline for maintenance12:10
patersoncNot sure I have any other news12:10
jkilava master had issues last Friday - did it auto-recover?12:10
patersoncYes, leter on Friday. I couldn't find a cause tbh12:11
jkicould be worse12:11
jkiok, other topics for testing?12:12
jki512:12
jki412:12
jki312:12
jki212:12
iwamatsu__https://lava.ciplatform.org/scheduler/device/qemu-prg-01 appears to be a configuration issue. Could you please check it?12:12
jkiwill forward this notice, yes12:13
iwamatsu__Thanks12:13
jkiBTW, "Physical access    Nobuhiro Iwamatsu" - not quite correct12:13
jkiI've seen that with more devices / labs12:13
jkipatersonc: who can fix that?12:14
patersoncThat worker needs to have `use_docker: true` set. Can only be done by the lab owner12:14
patersoncWe've had this issue before12:14
jkiNo, I was referring to that description entry12:15
jkibut that other hint is also useful, forwarded as well12:15
patersoncOh I see - not sure how some boards have been assigned to Iwamatsu-san. I can fix this in the admin interface12:16
jkiTIA!12:16
jkithen move on12:17
jki312:17
jki212:17
jki112:17
jki#topic AOB12:17
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:17
jki- LLM review tool news12:17
ulithe sltr scripts needed a bit of a fix for the new server setup12:17
ulipushed it this morning and sent an email12:17
pave1I got enough setup to talk to LLM via web interface.12:18
pave1Well, it is a LLM. :-)12:18
jkithen it's probably answering ;)12:18
ulimichael set the default to qwen 3.8. i haven't tried that at all yet.12:19
pave1Yeah. I have seen better models and I have seen worse models. Evaluating them is hard.12:19
ulii have a set of known-good and known-bad patches on top of 4.19 that i use for evaluation12:20
pave1That's a way to go.12:20
ulii wonder how/where i can put them up so they won't be confused with actual patches12:20
ulibecause they need to look realistic i cannot change authors or commit messages etc.12:20
pave1Are we evaluating for "will it break things" or "does it match stable kernel criteria"?12:20
ulifor the default prompt it's the former12:20
ulibut you can put whatever you want in it, of course12:21
ulii'm using it, among other things, to check if i accidentally pasted my passwords or keys in the commit message :)12:21
pave1Yeah, LLMs are versatile.12:21
jkiput those tests in a separate kernel tree, or just separate, clearly named branches?12:22
pave1jki: We don't want llm to find that tree :-)12:22
pave1I was thinking "highlight me patches where description says it is not for stable".12:22
pave1And perhaps patches having stable-dep-of: are useful as a test set, they don't usually match the published stable kernel rules.12:23
jkiyou cannot prevent that future trainings will find today's public work12:23
jkiand it may even be useful12:23
*** Dr_Who <Dr_Who!~tgall@70.35.96.200> has joined #cip12:23
jkibut during the inference, that may not be the case - and it could be avoided by working offline, against a local checkout12:24
uliwhat does a patch description say when it's _not_ for stable? i only know "Cc: stable", which is the opposite.12:24
pave1uli: People usually say something like "this does not fix a bug so don't put it into stable". There's12:26
pave1no common tag, and that's why LLM could be useful.12:26
uliwrite something like "analyze the commit message and determine if the commit is intended and suitable for inclusion in the stable kernel tree." and then add some criteria.12:27
ulishould work12:27
pave1ok.12:28
jki... and then review and fine-tune the criteria - or let the LLM look into past decisions12:28
jkigood - more on this?12:29
jki...or other AOBs?12:30
jki512:30
jki412:30
jki312:30
jki212:30
jki112:30
jki#endmeeting12:30
collab-meetbotMeeting ended Thu Aug 20 12:30:53 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:30
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/08/cip.2026-08-20-12.00.html12:30
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/08/cip.2026-08-20-12.00.txt12:30
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/08/cip.2026-08-20-12.00.log.html12:30
*** collab-meetbot changes topic to "Civil Infrastructure Platform Project. CIP mailing list at https://lists.cip-project.org/g/cip-dev | CIP kernel meeting every Thursday at 13:00 UTC | Find the meeting logs at https://ircbot.wl.linuxfoundation.org/meetings/cip/ and chat logs at https://ircbot.wl.linuxfoundation.org/logs/%23cip/"12:30
jkithanks!12:30
iwamatsu__Thank you12:30
ulithanks12:31
masamithank you12:31
pave1thank you!12:31
patersonciwamatsu__: Do you know how you became the "physical owner" for so many devices?12:32
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:32
iwamatsu__patersonc: No, I'm not sure the reason for that.12:33
patersoncOkay. I'll go through and fix them all to the correct person12:35
*** jki <jki!~jki@46.128.82.95> has quit IRC (Quit: Leaving)12:35
patersoncFixed12:45
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has joined #cip13:32
*** iwamatsu__ <iwamatsu__!~iwamatsu@user/iwamatsu> has quit IRC (Quit: Client closed)13:34
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 243 seconds)13:34
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip14:15
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has quit IRC (Remote host closed the connection)14:18
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has quit IRC (Ping timeout: 265 seconds)14:57
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has joined #cip14:58
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Remote host closed the connection)15:11
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip15:11
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has joined #cip15:15
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Read error: Connection reset by peer)15:15
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip15:16
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 252 seconds)15:20
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Server closed connection)15:39
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip15:39
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 241 seconds)15:39
*** tmerciai <tmerciai!~tmerciai@188.217.33.217> has joined #cip15:39
*** tmerciai <tmerciai!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 248 seconds)15:44
*** tmerciai <tmerciai!~tmerciai@188.217.33.217> has joined #cip15:45
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has joined #cip15:49
*** tmerciai <tmerciai!~tmerciai@188.217.33.217> has quit IRC (Ping timeout: 242 seconds)15:51
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has joined #cip15:58
*** tmerciai1 <tmerciai1!~tmerciai@188.217.33.217> has quit IRC (Read error: Connection reset by peer)16:00
*** tmerciai2 <tmerciai2!~tmerciai@188.217.33.217> has quit IRC (Remote host closed the connection)16:02
*** frieder <frieder!~frieder@88.130.219.91> has quit IRC (Remote host closed the connection)17:44
*** prabhakalad <prabhakalad!~prabhakar@106.219.124.208> has quit IRC (Quit: Konversation terminated!)19:10
*** rajm <rajm!~quassel@godforsaken.horse> has quit IRC (Server closed connection)21:34
*** rajm <rajm!~quassel@godforsaken.horse> has joined #cip21:35

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!