Thursday, 2023-05-11

*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)02:55
*** 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:14
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Remote host closed the connection)09:30
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip09:30
*** uli <uli!~uli@195.52.167.64> has joined #cip09:38
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip10:00
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip11:55
*** jki <jki!~jki@165.225.26.245> has joined #cip11:58
jkihi folks12:00
iwamatsuhello12:00
masamihi12:00
pave1hI!12:00
ulihello12:00
arisuthi12:01
*** jki_ <jki_!~jki@88.215.103.107> has joined #cip12:02
jki_ok, back - link issues12:03
jki_#startmeeting CIP IRC weekly meeting12:03
collab-meetbotMeeting started Thu May 11 12:03:19 2023 UTC and is due to finish in 60 minutes.  The chair is jki_. Information about MeetBot at http://wiki.debian.org/MeetBot.12:03
collab-meetbotUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:03
collab-meetbotThe meeting name has been set to 'cip_irc_weekly_meeting'12:03
*** collab-meetbot changes topic to " (Meeting topic: CIP IRC weekly meeting)"12:03
jki_#topic AI review12:03
*** collab-meetbot changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)"12:03
jki_1. create kernelci pipeline for buster images (arisut)12:03
arisutsorry I was busy this week going on next week on this12:03
jki_ok12:04
jki_anything else regarding AIs?12:04
*** jki <jki!~jki@165.225.26.245> has quit IRC (Ping timeout: 240 seconds)12:04
jki_312:04
jki_212:04
jki_112:04
jki_#topic Kernel maintenance updates12:04
*** collab-meetbot changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"12:04
ulii'm reviewing 6.1.2812:04
masamiThis week reported 9 new CVEs and 3 updated CVEs.12:04
pave1I'm revewing 6.1.28. It is a huge one.12:04
iwamatsuI did not work this week, sorry.12:05
jki_anything else?12:06
jki_312:06
jki_212:06
jki_112:06
jki_#topic Kernel release status12:06
*** collab-meetbot changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"12:06
jki_-4.412:07
ulion track12:07
jki_-4.1912:07
pave14.4-rt should be on track, too.12:07
jki_yep12:07
iwamatsu No new releases for LTS and RT...12:07
jki_did anyone reach out to RT already?12:08
jki_or was that for 5.10?12:08
pave1That was for 5.10.12:08
jki_right, we are still on track here12:08
jki_good12:08
jki_-5.1012:08
pave1As far as I can tell, 4.19-rt and 5.10-rt would be both useful for us.12:08
pave1At May 5th, 5.10.179-rt87  appeared in v5.10-rt-next.12:09
pave1If real release does not appear soon, I'll do the asking.12:09
jki_fine12:09
pave1https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/commit/?h=v5.10-rt-next12:09
jki_good12:11
jki_#topic Kernel testing12:11
*** collab-meetbot changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"12:11
patersonc[m]Hello12:11
patersonc[m]I have a question for kernel people - at the moment we aren't testing the CIP kernel trees with x86/arm/arm64 defconfigs. Should we be?12:11
pave1Good question.12:12
pave1Compile testing really would not hurt.12:12
pave1For x86 it should be testable on our targets.12:12
pave1For arm/arm64, I'm not that sure, but if it boots & works, we should make sure it keeps booting/working.12:13
patersonc[m]arm/arm64 defconfigs should run on the renesas boards AFAIK12:13
jki_I suspect the defconfigs also run in qemu12:14
patersonc[m]Is that all a "yes" then?12:14
pave1"Yes". :-)12:14
jki_+112:14
patersonc[m]Thanks12:14
patersonc[m]I'm not sure I have anything else this week12:15
jki_someone had a question for you last week...12:15
jki_pavel: "I may want to talk about 6.1 testing"12:15
arisutI would like to remember that KernelCI is already testing CIP kernels with arm and arm6412:16
pave1Yep. I guess we should either include gitlab.yml config in linux-6.1.x-cip tree.12:16
pave1Or maybe we want to use same system we use to test -stable kernels where .yml is not required.12:16
pave1Anyway we should start testing it.12:16
arisutand also RISCV12:16
patersonc[m]arisut: good point12:17
arisuthttps://github.com/kernelci/kernelci-core/blob/main/config/core/build-configs-cip.yaml#L20612:17
patersonc[m]pave1: i suggest you add the usual .gitlab-ci file to match up with the other CIP kernels12:17
pave1I'd eventually like to switch away from that, but it will do for now.12:18
pave1Can I copy the config from 5.10, or do I get version from you?12:18
patersonc[m]You can copy. Just change 5.10 -> 6.1 and it should work12:19
pave1Ok :-).12:19
jki_anything else on testing?12:22
arisut6.1 will soon be added to kernelci testing12:22
jki_512:23
jki_312:23
jki_212:23
jki_112:23
jki_4 :)12:23
jki_#topic AOB12:23
*** collab-meetbot changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)"12:23
jki_just a minor thing: next week is public holiday here, maybe elsewhere as well?12:24
pave1We had the public holiday on May 8th.12:24
pave1And May 1th. So no more of those for few months.12:24
jki_I may be able to participate, but I may also oversleep it if unlucky12:25
jki_would someone else take over the organization, just in case?12:25
iwamatsuI can take over.12:26
pave1Thank you :-).12:26
jki_thanks a lot!12:26
jki_anything else on AOBs?12:26
pave1Y.12:26
patersonc[m]ll12:26
pave1On Tuesday's meeting there was question if we use linux-stable gitlab mirror.12:27
jki_ah, right12:27
pave1I don't, but it should be asked here.12:27
patersonc[m]Do you mean https://gitlab.com/cip-project/cip-testing/linux-stable-rc/?12:28
pave1jki knows more. Yes, I believe it is that one. It is 10GB or so, and gitlab has size limits, so TSC wanted to know how important it is for us really, IIUC.12:29
jki_it was shrunk already IIUC, but that question remains valid12:30
patersonc[m]I added that repo recently because the kernel.org version was having connectivity issues. We use it in our stable-rc CI12:30
patersonc[m]I've now shrunk the repo to about 4Gb12:30
patersonc[m]s/4Gb/4GB/12:30
patersonc[m]So it's not an issue anymore12:30
jki_ok - then let us revisit this when the repo hits 10G again ;)12:32
jki_anything else?12:32
patersonc[m]yep12:32
patersonc[m]Did anyone see toscalix's question? https://ircbot.wl.linuxfoundation.org/logs/%23cip/%23cip.2023-05-09.log.html#t2023-05-09T08:16:3312:32
jki_not yet12:33
jki_well, we should likely ask for ownership transfer12:33
jki_not sure, thought, who all should be owner12:33
jki_+that functional account of the LF12:34
pave1LF admins want access to everything, so they can take this one, too? :-)12:34
pave1Or maybe it should be just deleted if we don't need it. But LF can do that too...12:34
jki_next question would be what to do with it then12:34
jki_we should at least keep the namespace reserved12:35
pave1Agreed.12:35
jki_yoshi and wolfgang are also members - whatever that means for them12:35
jki_ok, who will handle that github case?12:38
jki_if no one, I can write an email to him, yoshi and neal12:40
jki_anything else?12:41
jki_...if I had Agustin latest email address12:42
pave1github should have the address, no?12:42
jki_toscalix[m]: please contact me and yoshi on that github namespace12:42
jki_nope12:43
pave1Feel free to contact him thorugh:12:44
pave1Twitter: @toscalix12:44
pave1Mail:12:44
pave1Personal: toscalix(at)gmail(dot)com or abenito(at)kde(dot)org12:44
pave1IRC nickname: toscalix in irc.libera.chat12:44
pave1From https://toscalix.com/about/12:44
jki_ah, missed that12:45
jki_thanks12:45
jki_ok, then let's close for today12:45
pave1(Hmm. Not sure if I should be copying addresses into irc that is public & logged, but the address is publicly on web so hopefully that's ok).12:46
patersonc[m]:)12:46
jki_exactly :)12:46
jki_512:46
jki_412:46
jki_312:46
jki_212:46
jki_112:46
jki_#endmeeting12:46
collab-meetbotMeeting ended Thu May 11 12:46:43 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:46
collab-meetbotMinutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/05/cip.2023-05-11-12.03.html12:46
collab-meetbotMinutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/05/cip.2023-05-11-12.03.txt12:46
collab-meetbotLog:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/05/cip.2023-05-11-12.03.log.html12:46
*** 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:46
jki_thank you all!12:46
pave1Thank you!12:46
ulithanks12:46
iwamatsuthank you12:46
arisutthank you12:46
masamithanks12:46
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)12:47
patersonc[m]cheers12:48
*** uli <uli!~uli@195.52.167.64> has left #cip (Leaving)12:49
*** jki_ <jki_!~jki@88.215.103.107> has quit IRC (Quit: Leaving)14:09
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Remote host closed the connection)15:03
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)16:09
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 240 seconds)21:57

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