Thursday, 2026-06-04

*** m4t <m4t!~matt@2604:180:0:5d2::bad:beef> has quit IRC (Ping timeout: 272 seconds)05:34
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has joined #cip06:24
*** monstr <monstr!~monstr@nat-108f.starnet.cz> has quit IRC (Ping timeout: 248 seconds)06:28
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has joined #cip11:58
*** uli_ is now known as uli11:58
*** jki <jki!~jki@46.128.82.95> has joined #cip11:59
jkihi all12:00
iwamatsuhello12:00
pave1Hi!12:00
patersoncHello12:00
masamihello12:00
ulihello12:00
jkilet's go12:00
jki#startmeeting CIP IRC weekly meeting12:01
collab-meetbotMeeting started Thu Jun  4 12:01:02 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-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
collab-meetbotThe 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
jkinone12:01
jki512:01
jki412:01
jki312:01
jki212:01
jki112:01
jki#topic Kernel maintenance updates12:01
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:01
masamiThis week reported 172 new CVEs and 256 updated CVEs.12:01
ulidoing 4.4 atm12:01
pave1I am reviewing 6.1.91 and .92.12:01
iwamatsuI reviewed 6.12.88 and 89, and  I am reviewing 90 and 9112:02
jkianything to add?12:03
jki512:04
jki412:04
jki312:04
jki212:04
jki112:04
jki#topic Kernel release status12:04
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:04
jkiall on track12:04
jkiany issues ahead?12:04
pave1Yep. 6.1-rt-cip is due soon, and still12:04
pave1no suitable -rt. I may have to do release12:04
pave1without having -rt bae.12:04
pave1base.12:05
jkinext RT stable would be tomorrow, if you like to sync12:05
pave1If it is then great! :-)12:05
jkido you have the invite? I could forward otherwise12:06
pave1Aha, you mean stable rt meating, not stable rt release.12:06
pave1Yes, I have invite.12:06
jkinope, haven't heard of any release :)12:07
jkiyes, the call12:07
pave1Scheduling conflict on that one :-(, but I guess I can just email and ask.12:07
jkiok12:07
jkithen move on?12:08
jki512:08
jki412:08
jki312:08
jki212:08
jki112:08
jki#topic Kernel testing12:08
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:08
patersoncHi (sorry for the delay)12:09
patersoncI'm currently trying to get the T2H boards back online in the Renesas LAVA lab.12:10
patersoncMunich lab is still offline12:10
patersoncT2H bootloaders need an update, then they should work with KernelCI test jobs, then I'll merge that support12:11
patersoncI think that's it from me12:12
jkiMunich will be restored next week12:12
patersonciwamatsu: Can you let me know once you've updated your T2H board? Let me know if you need any help12:12
patersoncThanks jki12:12
jkiPrague should be fine now12:12
iwamatsupatersonc: OK12:13
patersoncThanks12:13
jkimore on testing?12:14
patersonc_o_12:14
jki512:15
jki412:15
jki312:15
jki212:15
jki112:15
jki#topic AOB12:15
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:15
jkiI had one topic12:15
jkiAI-assisted backport reviews, state & approaches12:15
patersoncVery on-trend12:16
jkiuli told me, and some should have been on CC, that he is using it for a while12:16
jkiI was wondering what others are doing12:16
jkiand if we could share skills or whatever centrally12:16
ulifor those who have not received that mail: i'm basically dumping all commits into an llm before release, with a large diff context and a slightly more verbose version of "check if this breaks something"12:17
uliworks pretty well for me, i.e. it finds things that would have otherwise slipped through12:17
patersoncnice12:18
pave1Yeah, I see how it can be useful with big context.12:18
pave1I don't have access to suitable llm that could be used for this.12:18
iwamatsuI'm testing Sashiko locally.12:18
patersoncIs there a thought/plan to convert to some kind of "official" CIP tooling? Or do we re-purpose/contribute to what Sasha has been working on?12:18
jkiis anyone tracking Sasha's work in more details?12:19
pave1For the tooling... there could be improvements to what we have, too.12:20
jkiI suspect it could eventually end up in sashiko12:20
pave1Half a year ago, 6.12, 6.1 and 5.10 would be in sync, so same patch would be reviewed once.12:20
pave1That no longer works.12:20
pave1Also maybe collecting outside notes ("John Doe reviewed this patch for 4.19") might be good.12:21
patersoncIs Sashiko more about reviewing patches sent to the ML, rather than selecting suitable patches for backporting?12:21
pave1patersonc: "Selecting patches for backporting" ... -stable was selecting way too much, so that was not normally a problem.12:22
pave1(But maybe AUTOSEL is paused for now or something).12:22
jkipatersonc: https://lwn.net/Articles/1073583/12:22
jki"Levin said that he had been working on getting Sashiko to review backports to stable trees and also needed to provide extra prompts in order to have it focus on the feedback he was looking for."12:23
patersoncAh, splendid :)12:23
jkiwas anyone in contact with Sasha already?12:24
jkishould we reach out and ask for some info?12:24
patersoncI think it could be something really good for CIP to collaborate on, it fits directly into what the project needs - same as stable12:25
jkiexactly12:25
jkiis there any mailing list for the sashiko work in general?12:28
iwamatsusashiko@lists.linux.dev12:29
jkiah, there is: https://lore.kernel.org/sashiko/ / sashiko@lists.linux.dev12:29
jkiyeah, just spotted as well,12:29
patersoncNice12:29
jkiso, step one would be researching for stable work on that list12:29
jkistep two could be asking Sasha on this list for updates, expressing our interest along this12:29
jkiuli: would you be interested in starting such a thread then?12:30
ulinot sure. :) i'll have a look at the list first.12:31
ulisee what they're actually doing.12:32
jkididn't spot anything about stable there yet, didn't find Sasha discussing there either12:32
jkiok, let's look at this and discuss next week again, ok?12:33
uligood.12:33
jkigood12:34
jkiother businesses for today?12:34
jki512:35
jki412:35
jki312:35
jki212:35
jki112:35
jki#endmeeting12:35
collab-meetbotMeeting ended Thu Jun  4 12:35:24 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:35
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/06/cip.2026-06-04-12.01.html12:35
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/06/cip.2026-06-04-12.01.txt12:35
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2026/06/cip.2026-06-04-12.01.log.html12:35
*** 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:35
jkithanks!12:35
ulithanks12:35
masamithank you12:35
iwamatsuThank you12:35
pave1Thank you!12:35
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:35
*** jki <jki!~jki@46.128.82.95> has quit IRC (Quit: Leaving)12:35
patersoncthanks12:35
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has joined #cip12:49
*** masami <masami!~masami@FL1-111-168-44-134.tky.mesh.ad.jp> has quit IRC (Client Quit)12:49

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