Thursday, 2023-06-22

« Wednesday, 2023-06-21 Index Friday, 2023-06-23 »
*** ironfoot <ironfoot!~pedroalva@user/ironfoot> has quit IRC (Server closed connection)02:00
*** ironfoot <ironfoot!~pedroalva@user/ironfoot> has joined #cip02:00
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip05:55
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip06:07
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has joined #cip08:24
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip08:59
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)09:25
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip10:45
*** masami <masami!~masami@FL1-122-133-157-25.tky.mesh.ad.jp> has joined #cip11:46
*** uli <uli!~uli@2001:4090:a246:8086:20a0:c5ca:9aae:6f74> has joined #cip12:00
*** jki <jki!~jki@62.156.206.27> has joined #cip12:01
jkihi all12:01
sietzeHi!12:01
ulihello12:01
pave1hi!12:01
arisuthello12:01
masamihi12:01
patersonc[m]hello12:01
jki#startmeeting CIP IRC weekly meeting12:02
collab-meetbotMeeting started Thu Jun 22 12:02:58 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:03
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:03
jki1. create kernelci pipeline for buster images (arisut)12:03
arisutcurrently it can create the three different versions of isar-cip-core https://storage.kernelci.org/images/rootfs/cip/20230615/qemu-amd64/12:04
jkimeans we are done (for now)?12:04
arisutbut I'm still finalizing things and also making the kernelci part12:04
jkiok, close but not yet :)12:04
arisutand will send the patch to isar-cip-core ML12:04
arisutyes12:05
jkigood12:05
iwamatsuhi all.12:05
jkihi!12:05
arisutwe made progress but not yet finished yet12:05
arisuthi iwamatsu12:05
jkianything else on AIs?12:07
jki512:07
jki412:07
jki312:07
jki212:07
jki112:07
jki#topic Kernel maintenance updates12:07
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:07
masamiThis week reported 11 new CVEs and 0 updated CVEs.12:07
ulireviewing 6.1.3412:07
pave1I did reviews -- 6.1.34 and .3512:07
iwamatsuI reviewed 6.1.33, 34 and 3512:08
pave16.1.x branch should be ready for release.12:08
iwamatsu;-)12:09
jkigood - anything else?12:11
jki512:12
jki412:12
jki312:12
jki212:12
jki112:12
jki#topic Kernel release status12:12
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:12
jki-4.412:12
ulion track12:12
jki-4.1912:12
iwamatsuon track12:13
jkirt as well?12:13
iwamatsuyes12:13
jki-5.1012:14
iwamatsuon track12:14
jkiindeed :)12:14
pave1-rt was released today.12:14
jkiperfect, thanks!12:14
jki-6.112:14
jkiready to launch, I heard12:14
pave1I'd say so.12:14
jkiwill then ask for the OK in the TSC meeting on monday12:15
pave1I will be based on older -stable by the12:15
pave1time we release it, but I guess that's okay.12:15
iwamatsu+112:15
jkiwe need to think about the release cycle we want to commit on here12:15
jki2x per month?12:16
patersonc[m]pave1: Is there time to update it to the latest stable before release?12:16
pave1I'd say 2x per month -cip, 1x per month -cip-rt and12:16
pave1move 5.10 to slower releases.12:16
jkiwhat would be the suggest there?12:17
jkiwould we have to make 5.10 slower to handle 6.1?12:17
pave1peterson -- it would be better to do -cip1 and then move it forward12:17
pave1using normall process.12:17
patersonc[m]Okay12:17
iwamatsuWho is in charge of 6.1? Pavel?12:18
pave1Iwamatsu?12:18
pave1You do the regular releases, I do the rt?12:18
iwamatsuOK, same as 5.10 and 4.19.12:19
pave1I'd suggest that.12:19
jkiiwamatsu: is that doable for you from your workload situation?12:20
iwamatsuYes, I have spoken to and agreed with my boss about it in this term.12:21
jkiok12:21
jkithanks12:21
iwamatsus/in this/from this/12:21
jkia lot :)12:21
jkiback to "would we have to make 5.10 slower to handle 6.1?" then12:22
jkiI want to be clear here when CIP members ask me this12:22
jkimaybe some will not be happy about that, maybe they are ok, can't predict12:23
pave1It would be good so that our workload does not grow too quickly.12:23
pave1We can probably handle the extra workload if it is really required.12:24
jkiok, some room for negotiation if needed12:25
pave1yes.12:25
jkijust checking https://wiki.linuxfoundation.org/civilinfrastructureplatform/start12:26
jkiwe have 2x per month for 4.19 still12:26
jkijust -rt is lagging behind there, significantly12:27
pave1I believe we should make 4.19-cip slower, too.12:27
jkilooking at who does regular releases, this is particularly a question for iwamatsu, right?12:28
pave1yes.12:28
iwamatsuYes, the 4.19 release cadence is widening.12:29
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)12:29
jkithen make it official there, ok, noted12:30
jkiand 5.10 is where we may react on feedback12:30
jkilet's see...12:30
jkireference targets for 6.1 initially?12:30
jkiqemu only?12:30
pave1The boards we have in the lab?12:31
pave1I assumed that when we got configs it meant they want it as reference hw.12:32
iwamatsuI recieved patches for confog of IPC27e and Renesas devices.12:33
iwamatsuRZV2M12:33
jkiso the list is not full12:34
jkiwhere did we put them formally, btw?12:34
jkiI mean the list12:34
jkiah, found: https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware12:34
patersonc[m]https://wiki.linuxfoundation.org/civilinfrastructureplatform/ciptesting/cipreferencehardware12:34
jkiso, we add qemu, ipc227e and ? there12:37
jkiRZV2M is already listed there?12:37
jkiHiHope?12:37
patersonc[m]RZ/V2M is a different board12:38
iwamatsumaybe V2M is other board12:38
patersonc[m]We're not proposing it as a reference board12:38
jkiok, then qemu and the ipc only12:38
patersonc[m]I'm happy for RZ/G1M iwg20m and RZ/G2M hihope to be reference boards12:38
jkifolks can always ask for more later12:38
jkibut do we have configs for 6.1 for those already?12:38
patersonc[m]Yes12:39
jkithen I'm adding those as well12:39
jkianything else?12:39
patersonc[m]Thanks12:40
jkithen let's move on...12:41
jki512:41
jki412:41
jki312:41
jki212:41
jki112:41
jki#topic Kernel testing12:41
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:41
arisutnothing other than the AI12:41
arisutfor me12:41
arisutpatersonc[m]:?12:42
patersonc[m]sietze and I have been working on a prototype squad server12:42
patersonc[m]Nothing to show yet though, but getting there12:42
jkicoool12:43
patersonc[m]That's probably about it other then prepping for next week12:43
jkidon't mention "next week prepping"... ;)12:44
jkiok12:44
patersonc[m]:P12:44
jkijust saw that our reference hardware table lists qemu-riscv64 only as candidate - I think that was accepted, no?12:45
pave1I should mention that Prague should be outside of range of terror attack on Zaporohzia...12:45
pave1jki -- not sure. We still have no serious risc-v hardware, so12:46
jki...at CIP12:46
pave1how much effort should go to risc-v still sounds like open question.12:47
jkiI'm using a VS2 in local "production" mode12:47
patersonc[m]It would be good to add the qemu for risc-v12:47
jkiVisionFive2 I mean12:47
patersonc[m]Nice12:47
patersonc[m]I keep meaning to hook one up to my lab at home12:47
jkiCIP committed on maintaining 5.10, and likely 6.1 as well, for riscv6412:48
pave1I'd say that reference board is strong commitment, but if Renesas wants that, lets do it.12:48
jkiand that implied to me that we commited on qemu at least12:48
patersonc[m]I think if we're supporting risc-v we at least need a qemu "reference board"12:49
pave1ok.12:49
jkiwe announced to support riscv with the kernel, not userland, not rt yet12:49
jkiI think the wiki is just outdated, but I can bring that up for clarification in the TSC as well12:50
patersonc[m]+112:50
iwamatsuI have it+112:50
pave1All the reference hardware will need to be approved by TSC, right? So these are just our suggestions...12:51
iwamatsu+112:51
jkiyes12:51
jkibut I think we got that already, let's clarify12:51
jkiok, then anything else on testing?12:52
jki512:52
jki412:52
jki312:52
jki212:52
jki112:52
jki#topic AOB12:52
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:52
jkisurvey update: who all will be in Prague now?12:53
arisutI will be away from 28 June to 18 July12:53
patersonc[m]o/12:53
ulio/12:53
jkio/12:53
iwamatsuo/12:53
pave1I'll be in Prague. Then week of travel.12:53
hiromotai[m]o/12:54
jkishould we skip irc next week then and rather have lunch together, maybe on Thursday?12:54
jki(besides all the other meetups we will have anyways ;)12:55
patersonc[m]+112:55
uli+112:56
pave1!12:56
pave1+112:56
iwamatsu+112:56
sietze+112:56
jkithen let's gather at lunch on Thursday at the CIP booth12:56
jkigreat!12:56
jkiany other business?12:57
jki512:57
jki412:57
jki312:57
jki212:57
arisutI will be away from 28 June to 18 July12:58
jki112:58
jkinoteded12:58
jki:)12:58
jkienjoy!12:58
jki#endmeeting12:58
collab-meetbotMeeting ended Thu Jun 22 12:58:25 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:58
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/06/cip.2023-06-22-12.02.html12:58
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/06/cip.2023-06-22-12.02.txt12:58
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/06/cip.2023-06-22-12.02.log.html12:58
*** 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:58
pave1thank you!12:58
sietzeThanks!12:58
ulithanks12:58
jkithank you all, and safe travels to Prague!12:58
arisutthanks you12:58
masamithanks12:58
*** masami <masami!~masami@FL1-122-133-157-25.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:58
hiromotai[m]thanks12:58
iwamatsuThank you12:59
*** masami <masami!~masami@FL1-122-133-157-25.tky.mesh.ad.jp> has joined #cip13:02
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip13:03
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)13:11
*** jki <jki!~jki@62.156.206.27> has quit IRC (Quit: Leaving)13:56
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)14:20
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)16:02
*** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Connection closed)16:17
*** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has joined #cip16:19
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip16:19
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)19:50
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 245 seconds)21:33
*** masami <masami!~masami@FL1-122-133-157-25.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)22:01
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip22:44
« Wednesday, 2023-06-21 Index Friday, 2023-06-23 »

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