Thursday, 2023-02-02

*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip09:14
*** \x <\x!~user@user/x/x-2225033> has left #cip10:05
*** uli <uli!~uli@175.176.15.168> has joined #cip11:59
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip12:50
*** jki <jki!~jki@195.145.170.194> has joined #cip12:56
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip13:00
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip13:00
jkiHi all!13:00
pave1Hi!13:00
alicefhi13:00
ulihello13:00
masamihi13:00
fbezdekaHi all!13:00
jkilet's go then13:03
jki#startmeeting CIP IRC weekly meeting13:03
collab-meetbot`Meeting started Thu Feb  2 13:03:16 2023 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.13:03
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:03
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'13:03
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"13:03
jki#topic AI review13:03
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"13:03
jki- enable more stable trees for testing (patersonc)13:03
jkichris is not around, so skip13:03
jkianything else?13:03
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
ulii reviewed 5.10.16413:06
masamiThis week reported 4 new CVEs and 3 updated CVEs.13:07
pave1I'm reviewing 5.10.166, .167.13:07
pave1I'm preparing for 4.4-rt update.13:07
jkipavel: uli is looking over your shoulder during that, right?13:10
pave1Not at the moment. It looks like we'll want to review pending patches together, but there's nothing critical in the pending list,13:12
pave1so I'll simply release rebased version.13:12
pave1It is "git merge" and "git rebase" when it works, there's not really much to look at :-)13:13
jkiok, that means you will continue doing that step also for future releases?13:13
jkiI also noticed that iwamatsu did the 4.4 release announcement - missing access for uli?13:13
pave1My understanding is that uli will do that at some point but not right now...?13:14
ulii assumed that was the standard procedure; i can do it myself from now on13:14
pave1Iwamatsu was doing all the -cip releases, so we kind of assumed it was supposed to work like that.13:14
jkiin the end, it is about workload sharing but also having redundancy in the process when we need to release and someone is not available13:15
jkiso, continue running in most efficient mode is fine if the latter is also ensured13:20
jkibut maybe revisit this when iwamatu is around as well13:20
pave1I believe we have enough access to do the -cip releases if we needed, but it was not needed so far :-).13:20
jkianything else?13:20
jki313:21
jki213:21
jki113:21
jki#topic Kernel release status13:21
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:21
jki- 4.413:22
uli4.4.302-cip72 is out13:22
pave1I'm looking at 4.4-rt.13:22
jkifine (just a bit delayed ;) )13:22
jki- 4.1913:22
jkieveryhing should be up-to-date - any issues ahead?13:23
pave1Nothing I'm aware of.13:23
jki- 5.1013:24
jkilooks like the same13:25
jkianything else?13:26
jki313:26
jki213:26
jki113:26
jki#topic Kernel testing13:26
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:26
alicefsent pull request for using cip-kernel-configs for 5.10.y-cip kernel on kernelci, added also riscv config https://github.com/kernelci/kernelci-core/pull/170513:26
jkiI added "status 6.1 LTS testing call of Greg" to the agenda13:29
jkidid we do anything in this regard?13:29
alicefnot on my knowledge13:30
jkiare we testing 6.1 by now? or is that the AI from above?13:31
alicefi will check with patersonc[m]13:31
jkiwhat else would be missing to speak up in that thread?13:31
pave1Even something as simple as running tests once with 5.10.X configs would be quite helpful.13:36
alicefkernelci will start doing that for 5.1013:37
pave1I meant test 6.1.X on our boards with 5.10.X configs.13:37
jkiexactly, and once we do that, we should drop a note to motivate Greg a bit more13:37
alicefi see13:38
pave1(Or if you can read the kernelci results and say "hey, according to kernelci it works ok on cip boards.. would be also helpful).13:39
jkianything else on testing?13:40
jki313:41
jki213:42
jki113:42
jki#topic AOB13:42
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"13:42
pave1There was query about 4.9 on the mailing list. I don't think we want to do that, but... :-)13:42
jkiwas nicely answered, yes :)13:42
jkidoes anyone know who is Dan Carpenter, and why cip is so often CC'ed now?13:44
jkinice to be recognized, was just wondering13:44
pave1He's long time linux contributor, I have Dan Carpenter <dan.carpenter@oracle.com> in my records.13:45
pave1But not sure what he has to do with CIP.13:45
jkiok - anything else?13:47
jki313:50
jki213:50
jki113:50
jki#endmeeting13:50
collab-meetbot`Meeting ended Thu Feb  2 13:50:20 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:50
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-02-13.03.html13:50
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-02-13.03.txt13:50
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/02/cip.2023-02-02-13.03.log.html13:50
*** 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:50
jkithank you all!13:50
ulithanks13:50
masamithank you13:50
pave1thank you!13:50
alicefthanks you13:50
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)13:52
*** uli <uli!~uli@175.176.15.168> has left #cip (Leaving)13:55
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip13:55
patersonc[m]Sorry I missed the meeting everyone. I had an unplanned visit to the school...15:02
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 248 seconds)15:21
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip15:25
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:44
*** jki <jki!~jki@195.145.170.194> has quit IRC (Quit: Leaving)15:58
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 260 seconds)22:45

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