Thursday, 2022-11-17

*** nero <nero!~nero@user/nero> has quit IRC (Quit: leaving)03:54
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip07:20
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:79db:6ae:bbd5:e201> has joined #cip07:21
*** uli <uli!~uli@175.176.15.150> has joined #cip09:59
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)11:12
patersonc[m]Just a heads up - I'll be 20-30 mins late for today's meeting11:12
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip11:14
*** masami <masami!~masami@fl1-125-198-44-131.tky.mesh.ad.jp> has joined #cip11:45
alicefpatersonc[m]: ok12:01
pave1Hi!12:02
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip12:02
masamihello12:02
alicefhi12:02
fbezdekahi12:02
ulihello12:02
pave1Jan indicated he might be late and that we should start w/o him.12:02
*** jki <jki!~jki@217.110.153.228> has joined #cip12:04
jkihi all12:04
jkias expected: late...12:04
pave1Hi!12:05
jkialready started?12:05
pave1Actually, sooner then expected. I guess you can start the meeting :-).12:05
jkiok :)12:05
alicefjki:no12:05
jki#startmeeting CIP IRC weekly meeting12:05
collab-meetbot`Meeting started Thu Nov 17 12:05:40 2022 UTC and is due to finish in 60 minutes.  The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot.12:05
collab-meetbot`Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:05
collab-meetbot`The meeting name has been set to 'cip_irc_weekly_meeting'12:05
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:05
jki#topic AI review12:05
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:05
jki1. Add qemu-riscv to cip-kernel-config - patersonc12:05
alicefpatersonc[m]: said that will be 20/30 minutes late12:06
jkiok12:06
alicefso we can skip this for now12:06
jki2. Create MR for disabling smc test in qemu - iwamatsu12:06
alicefworking on it12:06
alicefassing that to me12:06
jkiah, sure12:06
jkigood12:06
alicefI'm creating a PR for it12:07
fbezdekaMaybe you can mention me. I like to learn how to do that12:07
alicefjust removing smc_qemu from the test plans12:07
alicefok12:09
alicefi think we can go on ?12:11
fbezdekasure12:11
*** jki_ <jki_!~jki@2a00:20:300c:6dbd:fcb5:45c8:8028:e083> has joined #cip12:12
jki_ok, seems I was offline12:12
alicefI see jki got disconnected12:12
alicefwb jki_12:12
*** jki <jki!~jki@217.110.153.228> has quit IRC (Ping timeout: 260 seconds)12:12
jki_we didn't switch topics yet, right?12:12
fbezdekano, but we can go on12:12
alicefyes, please go on12:12
jki_#topic Kernel maintenance updates12:13
pave1I did reviews and 4.19-rt update.12:13
masamiThis week reported 2 new CVEs and 15 updated CVEs.12:13
ulii was down with a virus infection this week, no updates. will review 4.4-st-rc next.12:13
pave14.4-st-rc is also updated. I'd like uli to review it, then I can merge it to -cip and ask iwamatsu for release.12:14
jki_anything else?12:15
jki_btw, I can't re-claim meeting ownership for the bot, can I?12:15
pave1Your other identity disconnected, so maybe you can claim it now?12:16
jki_how?12:16
alicefyou need to ghost the other identity12:17
*** jki <jki!~pavel@jabberwock.ucw.cz> has joined #cip12:17
pave1let me try.12:17
pave1312:17
pave1212:17
pave1112:17
jki#topic kernel testing12:17
*** collab-meetbot` changes topic to "kernel testing (Meeting topic: CIP IRC weekly meeting)"12:17
alicefno news other than the pr from me12:18
alicefpatersonc[m] is not here12:18
jki_ok, then let go to the new topic section now: #topic Kernel release status12:19
jki#topic Kernel release status12:19
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:19
jki_4.412:19
pave14.4-st-rc is also updated. I'd like uli to review it, then I can merge it to -cip and ask iwamatsu for12:19
pave1+release.12:20
jki_estimated release roughly when?12:20
pave1Process should be straightforward when Uli reviews it.12:20
ulii haven't looked how much work that is yet12:21
ulibut i guess it will be done until next meeting12:22
jki_that would be great12:22
jki_we are late here as discussed12:22
jki_how about 4.4-rt after that?12:22
pave1That should be fairly straightforward, too. Assuming there are no -rt specific changes in 4.9-rt; I have not yet had to deal with that.12:23
jki_please have a look then soon as well12:23
jki_ok12:24
pave1Ok, will do. Thanks.12:24
jki_4.19 / 5.10 (summarizing)12:24
jki_I've seen recent releases for all12:24
* patersonc[m] arrives12:24
pave14.19-rt was done this week, 5.10-rt was this month, we should be ok there.12:24
jki_anything to add for those kernels that could delay the next ones?12:24
jki_if not, moveing on12:26
pave1Not currently aware of anything.12:26
jki_patersonc[m]: anything to add to "kernel testing"?12:26
jki_or to your riscv AI? ;)12:26
patersonc[m]I was going to say that things seems table now on Gitlab - has anyone seen any issues?12:26
jki_seems not...12:28
patersonc[m]On another topic, I noticed this week that a number of branches in the gitlab repo were out of sync with the kernel.org repo. I've now fixed this and the mirroring should be working properly now.12:28
patersonc[m](The linux-cip repo)12:28
jki_what was causing this?12:29
patersonc[m]I guess something was pushed to our gitlab fork before/instead of the kernel.org repo12:29
patersonc[m]So when it tried to pull an update it stopped because the branch had diverged12:29
patersonc[m]I've changed the pull settings now so that the pulling should overwrite diverged branches12:30
jki_hopefully in the right direction ;)12:30
patersonc[m]And that it only pulls for "protected" branches - which are set to the ones present in the kernel.org repo12:30
patersonc[m]:)12:30
patersonc[m]I have one more repo related topic...12:31
patersonc[m]On https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/refs/heads there are three branches we don't update at all - linux-4.4.y, linuc-4.19.y and master12:31
patersonc[m]Should we remove them?12:31
patersonc[m]Or start updating them from upstream?12:31
jki_do we have a use case for them on gitlab?12:32
patersonc[m]Not that I'm aware of12:32
pave1master is also unused, I'd say.12:33
jki_then drop them, rather than having stale versions12:33
jki_maybe master is different, though12:34
patersonc[m]I think the master used to = 4.4-cip back in the day12:34
pave1Well, after latest push against word "master", people have been renaming it to main, and others.12:35
pave1So there's good chance that nothing depends on the master branch...?12:35
jki_if it was stale and pointing to a strange base before, very likely12:35
jki_any other branching topics?12:37
jki_actually, we are already in...12:37
jki_#topic AOB12:37
jki#topic AOB12:37
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:37
jki_anyone anything?12:37
jki_if not: dear ghost of mine, please close :)12:38
pave1512:39
pave1412:39
pave1312:39
pave1212:39
pave1112:39
jki#endmeeting12:39
collab-meetbot`Meeting ended Thu Nov 17 12:39:15 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:39
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-17-12.05.html12:39
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-17-12.05.txt12:39
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2022/11/cip.2022-11-17-12.05.log.html12:39
*** 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:39
patersonc[m]:)12:39
*** jki <jki!~pavel@jabberwock.ucw.cz> has quit IRC (Quit: Leaving)12:39
pave1Thank you!12:39
ulithanks12:39
masamithank you12:39
jki_thank you all, happy hacking!12:39
*** jki_ <jki_!~jki@2a00:20:300c:6dbd:fcb5:45c8:8028:e083> has quit IRC (Quit: Leaving)12:39
*** masami <masami!~masami@fl1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:40
*** uli <uli!~uli@175.176.15.150> has left #cip (Leaving)12:40
patersonc[m]jki_: Can I nudge you again on the Jailhouse patches from Prabhakar?12:40
patersonc[m]Well, too late to ask if I can - I just did nudge ;)12:40
alicefthank12:43
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip12:47
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)14:03
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip14:35
*** tobsch <tobsch!~quassel@2a02:810d:4bc0:2020:79db:6ae:bbd5:e201> has quit IRC (Ping timeout: 256 seconds)16:34
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Read error: Connection reset by peer)19:19
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip19:21
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 256 seconds)22:53

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