Thursday, 2026-07-16

*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip04:34
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)04:38
*** frieder <frieder!~frieder@i59F664E6.versanet.de> has joined #cip06:37
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has joined #cip06:55
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 268 seconds)07:47
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has joined #cip07:48
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has quit IRC (Remote host closed the connection)08:10
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has joined #cip08:11
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 244 seconds)08:34
*** tmerciai1 <tmerciai1!~tmerciai@188.217.48.55> has joined #cip08:34
*** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has quit IRC (Quit: Konversation terminated!)08:49
*** prabhakalad <prabhakalad!~prabhakar@97e54365.skybroadband.com> has joined #cip08:57
*** tmerciai1 <tmerciai1!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 248 seconds)09:50
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has joined #cip09:50
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 264 seconds)10:08
*** tmerciai1 <tmerciai1!~tmerciai@188.217.48.55> has joined #cip10:09
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has joined #cip11:54
*** jki <jki!~jki@62.156.206.18> has joined #cip11:59
jkihi all12:00
pave1Hi!12:00
ulihello12:00
masamihello12:00
patersonchi12:00
jki#startmeeting CIP IRC weekly meeting12:01
collab-meetbot`Meeting started Thu Jul 16 12:01:05 2026 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:01
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:01
jki#topic AI review12:01
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:01
jki- start blogpost draft [iwamatsu-san]12:01
iwamatsuhello12:01
iwamatsuno update12:01
iwamatsu> blogpost draft12:01
jkiok - I guess we will eventually be asked for a potential slot date12:01
iwamatsuI am going to start tomorrow.12:02
jkigood, just let us know if we should help anywhere12:02
jkino other AIs recorded12:02
jki512:02
jki412:02
jki312:02
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
masamiThis week reported 3 new CVEs and 0 updated CVEs.12:03
pave1I was reviewing 6.12.95 nad various patch series on the mailing list.12:03
pave1Bascially catching up after travels.12:03
uliworking on 4.19; 4.4 is still missing a few reviews12:03
iwamatsuI am reviewing 6.12.94.12:03
pave1uli: that batman-adv thingines?12:03
pave1thingies?12:03
ulithat's what i mean12:04
pave1Ok, I'll put them back on my todo list.12:04
uliit's not strictly necessary; iiuc iwamatsu-san reviewed all of it12:04
pave1("What is batman and why are we reviewing that? Is there some actual user? Why is it enabled in our configs?")12:05
uliexcellent questions :)12:05
jkiwhich batman are we talking about? :)12:05
jkiand which config asks for him?12:05
pave1-stable patches are full of batman...12:06
pave1Like this: 270f518e2aab7 batman-adv: tt: fix negative tt_buff_len12:06
jkiCONFIG_BATMAN_ADV is fairly often set...12:06
ulijki: moxa_* and siemens-i386-rt (the latter has basically everything enabled :( )12:07
pave1Yeah. And I'm tired of that particular superhero :-).12:07
jkithe latter is quite old12:07
jki4.19.y/x86/siemens_iot2000.config:# CONFIG_BATMAN_ADV is not set12:08
jkiwe do not feel guilty here ;)12:08
pave1It was nontrivial part of 4.4-st review.12:08
pave1It is some kind of mesh networking IIRC. And we might want to take a second look if we really need it.12:08
jkimoxa config pull it in in 4.4.12:09
jkisiemens_i386-rt_defconfig do on 4.19 and 5.10, ok...12:09
jkianyway, please raise that on the mailing list towards all affected config owners12:11
pave1If someone could take a look and perhaps remove it from the config. Another one probably not needed is qla2xxx.12:11
pave1Ok, will do.12:11
jkiplease also provide reasons along that so that we can forward12:12
pave1(There's a ton of unused stuff, but these have people actually patching them, so they cause some load.)12:12
jkisure12:12
jkisome configs might have received too little feature reviews before we accepted them...12:13
jkiok - more maintenance topics?12:13
jki512:14
jki412:14
jki312:14
jki212:14
jki112:14
jki#topic Kernel release status12:14
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:14
jki4.4 regular and 4.19-rt are due12:14
jki4.4, we already discussed - anything about 4.19-rt?12:15
pave1I need to take a look. Should be ok.12:15
jkioh, 6.1 is due as well12:15
jkiflipped after a12:15
iwamatsuYes, I am going to do it.12:16
jkiafter I ran the script this morning12:16
jkigood12:16
jkiso, no issues in sight, just work :)12:16
jkianything to add?12:16
jki512:16
jki412:16
jki312:16
jki212:17
jki112:17
jki#topic Kernel testing12:17
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:17
arisutworking on a new release of kci-dev with mcp features12:17
patersoncNice12:17
patersoncI've no updates this week12:18
jkianything else on testing?12:19
jki512:19
jki412:20
jki312:20
jki212:20
jki112:20
jki#topic AOB12:20
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:20
jkinews from cip-llm-gateway.ciplatform.org: it's basically running12:20
pave1Nice :-). What is needed to play with it? (And what to expect?)12:20
jkiuli noticed some thermal... limitations, though, we are looking into that12:20
ulii should be able to provide the scripts and instructions for use by next meeting12:21
jkithat sounds great!12:21
ulithe gpu runs hot, so it's throttled and performance is mediocre.12:21
jkiyeah, we need to understand that12:22
pave1What should be my expectations, compared to gpt-5.4-nano (duck.ai)?12:22
ulii haven't done any large-scale experiments with cloud models, but12:22
ulifrom what limit experience i have, the regular free chatgpt models make the same mistakes :)12:23
pave1Ok, that sounds good :-). My local experiments ... were not comparable to gpt-5.4-nano, not even remotely.12:24
jkiI have various more advanced models at hand and can also do cross checks where useful12:24
jkiwe as CIP also have Codex access now12:25
jkivia me - drop me data and prompts12:25
jkisecurity insensitive ones for now, more later12:25
pave1So what would be expectations from codex? "Write me a calculator application for Commodore 64, in Pascal"?12:26
jkiuse Uli's setup eventually, just with a different backend12:26
pave1Ok.12:26
jkiother businesses for today?12:28
jki512:29
jki412:29
jki312:29
jki212:29
jki112:29
jki#endmeeting12:29
collab-meetbot`Meeting ended Thu Jul 16 12:29:31 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:29
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/07/cip.2026-07-16-12.01.html12:29
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/07/cip.2026-07-16-12.01.txt12:29
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/07/cip.2026-07-16-12.01.log.html12:29
*** 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:29
jkithanks!12:29
pave1Thank you!12:29
ulithanks12:29
iwamatsuThank you12:29
masamithank you12:30
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:30
*** jki <jki!~jki@62.156.206.18> has quit IRC (Quit: Leaving)12:30
*** tmerciai1 <tmerciai1!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 266 seconds)13:40
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has joined #cip13:40
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 273 seconds)13:48
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has joined #cip13:48
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 263 seconds)14:04
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has joined #cip14:05
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 272 seconds)14:11
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has joined #cip14:11
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has quit IRC (Remote host closed the connection)14:23
*** frieder <frieder!~frieder@i59F664E6.versanet.de> has quit IRC (Remote host closed the connection)15:38
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has joined #cip17:30
*** tmerciai1 <tmerciai1!~tmerciai@188.217.48.55> has joined #cip17:34
*** tmerciai <tmerciai!~tmerciai@188.217.48.55> has quit IRC (Remote host closed the connection)17:35
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has joined #cip17:37
*** tmerciai1 <tmerciai1!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 244 seconds)17:39
*** tmerciai1 <tmerciai1!~tmerciai@188.217.48.55> has joined #cip17:45
*** tmerciai2 <tmerciai2!~tmerciai@188.217.48.55> has quit IRC (Ping timeout: 266 seconds)17:48
*** noctux <noctux!~noctux@user/noctux> has quit IRC (Read error: Connection reset by peer)17:50
*** noctux <noctux!~noctux@user/noctux> has joined #cip17:53
*** collab-meetbot <collab-meetbot!~supybot@ec2-35-167-58-160.us-west-2.compute.amazonaws.com> has joined #cip20:19
*** ChanServ sets mode: +o collab-meetbot20:19
*** collab-meetbot` <collab-meetbot`!~supybot@ec2-34-211-101-61.us-west-2.compute.amazonaws.com> has quit IRC (Remote host closed the connection)20:26
*** Dr_Who <Dr_Who!~tgall@70.35.96.200> has quit IRC (Ping timeout: 276 seconds)23:18

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