Thursday, 2023-07-20

*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip01:52
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip05:43
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip08:32
*** masami <masami!~masami@FL1-211-135-148-63.tky.mesh.ad.jp> has joined #cip11:55
*** uli <uli!~uli@2001:4090:a247:81aa:4a3f:74bf:d382:d6f5> has joined #cip11:56
*** jki <jki!~jki@62.156.206.45> has joined #cip11:58
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Ping timeout: 246 seconds)11:58
jkihi everyone!12:00
ulihello12:00
iwamatsuhi12:00
masamihello12:00
arisut_hi12:00
patersonc[m]Hellooo12:00
patersonc[m]arisut_: Welcome back12:01
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip12:01
jkiok, let's go12:02
jki#startmeeting CIP IRC weekly meeting12:02
collab-meetbotMeeting started Thu Jul 20 12:02:16 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:02
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:02
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:02
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:02
jki#topic AI review12:02
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:02
jki1. create kernelci pipeline for buster images (arisut)12:02
pave1Hello!12:02
arisut_no news on this12:03
jkiok12:03
jkianother AI I forgot:12:03
jki2. draft press release on 6.1 release (jan)12:03
jkitodo...12:03
jkianything else?12:04
pave1Nothing from last week, IIRC>12:04
jki#topic Kernel maintenance updates12:04
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:04
pave1Reviews on 6.1.39. This is huge one.12:05
ulisame here12:05
masamiThis week reported 12 new CVEs and 4 updated CVEs.12:05
iwamatsuI am reviewing 6.1.39.12:05
masamistarted tracking the linux-6.1.y-cip-rt branch on cip-kernel-sec.12:05
pave1There's a lot of patches to be applied to -cip.12:06
pave11. Watchdog stuff Jan submitted -- I propose we take that one, it does not look scary and follows the rules.12:06
pave12. Patches from -next submitted by Renesas -- I propose we wait there.12:07
pave1(Waiting for patches to reach mainline before they can be applied, as usual).12:07
jkianything else?12:09
iwamatsuabout 1 , I agree, but I suggest posting to stable first.12:09
jkiI can try that as well12:09
jkiwhatever you prefer12:09
pave1Well, I'm not sure bug is "severe enough" to meet stable rules.12:10
pave1It is a showstopper for us, but the watchdog still works "as well as" other drivers in tree.12:10
jkistable could argue it's a feature, but the absence of reaction from the watchdog maintainers de-motivated me to go for stable12:11
pave1SO, lets re-evalute this one in 14 days?12:13
jkiand do nothing till then, or what now?12:13
pave1Well, my proposal would be to just take patches and ignore the stable. It is not "clearly stable" material.12:14
pave1If that is not acceptable, the other proposal is "jki submits it to stable, and either stable takes it or we take it after two weeks".12:15
jkiIf I find some cycles, I can try the submission12:15
jkiok, other kernel maintenance topics?12:16
jki512:16
jki412:16
jki312:16
jki212:16
jki112:16
jki#topic Kernel release status#12:16
*** collab-meetbot changes topic to "Kernel release status# (Meeting topic: CIP IRC weekly meeting)"12:16
jki-4.412:16
ulino news, on track12:16
jki-4.1912:17
iwamatsuon track12:17
pave1all -rt releases should be on track.12:17
jki-5.1012:17
iwamatsuon track12:17
jki-6.112:18
jkijust release... will that huge .39 delay things for us?12:18
pave1That's usual "rc1 is huge", I don't think it should cause any issues.12:19
iwamatsuI think so.12:19
jkiok12:20
jkithen move on12:20
jki#topic Kernel testing12:20
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:20
patersonc[m]I don't have much12:21
patersonc[m]sietze , do you have any updates on squad?12:21
sietzeStill working on a PoC for Test reporting with SQUAD12:22
sietzeWe set up a test with CIP kernel testing in the CIP playground group12:22
sietzeAlmost there, but unfortunately not something to show, yet12:23
jkinext week then ;-)12:24
patersonc[m]:)12:24
sietzeYes, I hope so, but Chris has to show it then12:24
patersonc[m]Ha12:24
sietzeVacation for the next 3 weeks ...12:24
jkianything else on testing?12:25
jkimaybe you could already have a look at https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware12:25
jkithere are some white fields, and maybe someone know where we are with those12:26
patersonc[m]Okay12:26
patersonc[m]Make it an action for me12:26
jkiok12:26
patersonc[m]I think all platforms are booting okay12:27
patersonc[m]So probably Y for everything if that's what we aim to support12:27
patersonc[m]We were originally waiting for members to say what boards they wanted to support12:27
jkiadding "T"s is a technical step, the "Y"s are the formal ones12:27
patersonc[m]Okay12:28
jkigood, move on?12:28
jki512:29
jki412:29
jki312:29
jki212:29
jki112:29
jki#topic AOB12:29
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:29
jkiplease cross-check https://wiki.linuxfoundation.org/civilinfrastructureplatform/start#kernel_maintainership12:29
iwamatsuok, I will check it.12:30
jkithen I need a substitute for the next two meetings12:30
jkiI'll be back on August 1012:30
patersonc[m]I'm away next week12:30
ulime, too12:31
jkiwho will be there next week at all?12:31
iwamatsuo/12:32
masamio/12:32
pave1I'll be here. I'll do some travels in August.12:32
jkithen I would leave it up to you three if you want to sync next week12:33
jkinext but one, there will be more?12:33
jkiwho would be able run that meeting?12:33
pave1I can take the next one, and likely the one after that, too.12:34
pave1If not, we can solve it on the next meeting :-).12:34
jkiok, thanks!12:35
jkiother topics for today?12:35
jki512:36
jki412:36
jki312:36
jki212:36
jki112:36
jki#endmeeting12:36
collab-meetbotMeeting ended Thu Jul 20 12:36:30 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:36
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/07/cip.2023-07-20-12.02.html12:36
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/07/cip.2023-07-20-12.02.txt12:36
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/07/cip.2023-07-20-12.02.log.html12:36
*** 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 12: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:36
pave1Thank you!12:36
ulithanks12:36
jkithank you, happy summer vacations!12:36
iwamatsuthank you12:36
arisut_thanks you12:36
masamithank you12:36
sietzeThanks!12:36
*** masami <masami!~masami@FL1-211-135-148-63.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:37
*** jki <jki!~jki@62.156.206.45> has quit IRC (Quit: Leaving)13:26
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)14:48
*** uli <uli!~uli@2001:4090:a247:81aa:4a3f:74bf:d382:d6f5> has left #cip (Leaving)14:51
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:20
*** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 272 seconds)17:52
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 245 seconds)21:42

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