Thursday, 2023-02-16

*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip07:13
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip07:28
*** uli <uli!~uli@175.176.15.142> has joined #cip12:40
*** jki <jki!~jki@88.215.103.113> has joined #cip12:47
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip12:59
jkihi all13:01
ulihello13:01
iwamatsu`hi!13:01
alicefhi13:01
masamihi13:01
patersonc[m]Mornin13:01
jki#startmeeting CIP IRC weekly meeting13:02
collab-meetbot`Meeting started Thu Feb 16 13:02:49 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:02
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:02
jki#topic AI review13:02
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:02
jki1. enable more stable trees for testing (patersonc)13:03
pave1Hello...13:03
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip13:03
patersonc[m]No updates yet13:03
jkiany help needed?13:04
patersonc[m]Just time, sorry13:04
jkinp13:04
jki2. report 6.1 test plan to LKML (pavel)13:05
patersonc[m]There's nothing that hard to do, unless the kernel doesn't want to run on our boards13:05
pave1Waiting for (1).13:05
jkiyeah, just to track both13:05
jkiother AIs?13:05
jki313:06
jki213:06
jki113:06
jki#topic Kernel maintenance updates13:06
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:06
masamiThis week reported 2 new CVEs and no updated CVEs.13:06
uliwas out most of the week, no updates. still reviewing 5.10.168.13:07
pave1I'm currently travelling, but did few reviews on 5.10.X.13:07
iwamatsu`I reviewd 5.10.16813:07
jkianything else here?13:09
jki313:10
jki213:10
jki113:10
jki#topic Kernel release status13:10
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:10
jki- 4.413:10
ulion track. 4.14 patches are a bit less likely to apply cleanly than 4.9 did.13:10
ulibut that's expected, i guess13:11
pave1IIRC -rt in 4.4 and 4.19 should be on track13:11
jki- 4.19 (partly already answered)13:11
iwamatsu`no issue. on track.13:12
jki- 5.1013:12
iwamatsu`same 4.19.13:12
jkigreat13:12
jki#topic Kernel testing13:12
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:12
pave1uli -- I believe -stable approach is 'if it does not apply we drop it... So you simply did not  see the problematic patches.13:12
pave15.10-rt13:12
pave1I believe that one should be done when we have version match.13:13
alicefupdated the Use cip-kernel-configs for kernels (5.10.y-cip, 4.4.y-cip) PR to kernelci-core13:13
patersonc[m]Thank you alicef13:13
alicefremoved rpc_defconfig on all the version as is just giving errors13:14
alicefbut noticed now that I maybe missed the kselftest fragments that I will add in the next days13:14
alicefcurrently testing it with kernelci staging13:15
alicefhttps://github.com/kernelci/kernelci-core/pull/170513:17
jkigreat13:18
alicefI'm currently considering what other defconfig we don't need13:18
alicefoh and also added risv configuration for 5.10.y-cip13:19
alicefusing cip-kernel-config13:19
jkiwhich is THE defconfig13:20
jkifbezdeka: you are trying to follow up with Daniel regarding stable RT, kernel-ci & Co.13:21
fbezdekaRight. But no response so far...13:21
jkitoo fresh, let's see13:21
jkianything else?13:23
patersonc[m]Not from me13:24
jki313:25
jki213:25
jki113:25
jki#topic AOB13:25
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:25
pave1There may be another CPU bug being worked around by mainline.13:26
jkiIntel again?13:26
alicefmmm looks like riscv cip-kernel-config work but is not catching any riscv test. problably still need to implemented. https://staging.kernelci.org/build/id/63ee16e8dbf35ba5f59d58c6/13:26
pave1intel probably. will need to investigate.13:27
jkino risc-v at all in kernel-ci so far??13:27
jkipavel: where did you pick this info up from? strange commits or direct channels?13:28
alicefthere is already riscv, just is missing some specific tests framgments13:28
pave1jki -- diffstat, so far.13:29
jkiwell, then let's watch the news13:31
jkianything else?13:31
alicefI probably need to look into risc-v fragments, will look into it in the next days13:31
jkialicef: TIA!13:32
jkithen, closing in...13:33
jki313:33
jki213:33
jki113:33
jki#endmeeting13:33
collab-meetbot`Meeting ended Thu Feb 16 13:33:16 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:33
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-16-13.02.html13:33
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-16-13.02.txt13:33
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-16-13.02.log.html13:33
*** 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/"13:33
jkithanks, all!13:33
pave1Thank you!13:33
alicefthanks13:33
masamithank you13:33
ulithanks13:33
iwamatsu`thank you13:33
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving)13:35
*** jki <jki!~jki@88.215.103.113> has quit IRC (Quit: Leaving)13:35
*** uli <uli!~uli@175.176.15.142> has left #cip (Leaving)13:36
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip13:40
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:56
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:45
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)19:56
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip20:02
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)20:28
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip22:35
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 246 seconds)22:46
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)23:01

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