Thursday, 2023-03-02

« Wednesday, 2023-03-01 Index Friday, 2023-03-03 »
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip06:47
*** shoragan <shoragan!~shoragan@user/shoragan> has quit IRC (Remote host closed the connection)07:49
*** shoragan <shoragan!~shoragan@user/shoragan> has joined #cip07:49
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip08:38
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)09:20
*** uli <uli!~uli@195.52.139.214> has joined #cip09:46
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip11:08
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has joined #cip12:42
*** jki <jki!~jki@165.225.26.243> has joined #cip12:57
*** sietze <sietze!~sietze@msw-v.fe.bosch.de> has joined #cip12:57
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has joined #cip12:58
*** sietze <sietze!~sietze@msw-v.fe.bosch.de> has quit IRC (Client Quit)12:59
*** sietze_van_buure <sietze_van_buure!~sietze_va@msw-v.fe.bosch.de> has joined #cip13:00
jkihi all13:00
masamihi13:00
ulihello13:00
alicefmHi13:00
*** sietze_van_buure is now known as sietze_v_buuren13:00
*** pave1 <pave1!~pavel@jabberwock.ucw.cz> has joined #cip13:00
*** sietze_v_buuren is now known as sietze13:01
patersonc[m]Hello13:01
jkisietze_v_buuren: new "face", welcome!13:02
sietzeHello!13:02
jkiok, let's start slowly13:03
jki#startmeeting CIP IRC weekly meeting13:03
collab-meetbot`Meeting started Thu Mar  2 13:03:12 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
jki1. enable more stable trees for testing (patersonc)13:03
patersonc[m]I kicked off some tests with this13:04
patersonc[m]With 5.15 and 6.1, BBB didn't boot13:04
patersonc[m]And for 5.15 and 6.1 the de0-nano dts wasn't built13:04
patersonc[m]Perhaps both issues are config issues13:05
jkinot unlikely13:05
patersonc[m]If anyone is interested, 5.15 pipeline: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/78674157613:05
jkitried upstream defconfig instead?13:05
patersonc[m]6.1: https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/78678035413:05
patersonc[m]jki: Not yet13:05
patersonc[m]Well, Arm defconfig is built, haven't checked if it runs on bbb though13:06
patersonc[m]Anyway, WIP13:07
jkiok, great13:07
jki2. report 6.1 test plan to LKML (pavel)13:07
jkijust listing, depends on 1 to be ready enough13:07
jkior is it?13:07
patersonc[m]We could run with what we have. EIther accept the 2 test jobs that will fail or remove them, until it's fixed13:08
jkipavel: would you like to move forward?13:09
pave1Yes, can do.13:09
jkiperfect13:09
pave1Id remove jobs for now.13:09
jkianything else regarding AIs?13:10
jki313:12
jki213:12
jki113:12
jki#topic Kernel maintenance updates13:12
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)"13:12
ulii tested and pushed 4.4 rc and sent request for review13:12
masamiThis week reported 22 new CVEs and 4 updated CVEs.13:12
masamiI think new CVEs are not so critical vulnerabilities.13:13
pave1I'm reviewing 5.10.170 and 171.13:13
jkianything else to report/discuss?13:16
jki313:16
jki213:16
jki113:16
jki#topic Kernel release status13:16
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)"13:16
jki- 4.413:16
uliready to be released, waiting for the review thumbs up13:17
pave1Will take a look. Sorry  for delay.13:17
jkicool13:17
jkiwhen is -rt due again?13:17
ulinext time13:18
uliiirc13:18
jkiok13:18
jki- 4.1913:18
jkiiwamatsu is missing, but maybe someone else has infos13:18
jkithen move on13:20
jki- 5.1013:20
jkilikely the same13:20
jkianything to report regarding -rt?13:20
pave1both 5.10 and -rt should be on track.13:21
jkigood13:21
jki#topic Kernel testing13:21
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)"13:21
patersonc[m]Hellooo13:21
jkiyes, we can read you13:22
patersonc[m]Ha, sorry13:22
alicefmWaiting staging to get new kselftest changes for testing it with cip kernel configs13:22
patersonc[m]I don't have much to add from the TSC earlier or the AI above13:23
patersonc[m]Main TODO is to interact with Bosch and delegate some tasks13:23
jkiah, great13:23
jkianything else regarding testing?13: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
jki- LTS....13:25
jkihow to talk to Greg?13:25
jkiwho can talk to Debian kernel team?13:26
pave1Greg responds to emails.13:26
jkibetter public?13:26
jkior private first?13:26
jkiand who wants to start this?13:27
pave1I believe that depends on what we want...13:27
pave1Public is better.13:27
jkiare Greg's concerns somewhere public already?13:28
jkiand plans?13:28
jkinot that we carry some "news" to the world13:28
jkipublic is the reduced lifespan of 5.15 and 6.1 at least13:29
jkiand the trend13:29
pave1I'm getting my lts news from you.13:29
jkiand I got them from LF emails (and now they are archived here, publicly :) )13:30
patersonc[m]What's our goal? Try and get him to extend LTS to 4/6 years again?13:30
patersonc[m]We'd need to get more then just CIP on board to commit to testing & support etc.13:30
jkifirst of all understand what it would take from his POV13:30
jkiexactly13:30
jkiwe should be honest with ourselves and him that we alone can't fix it13:30
pave1I believe we should write somewhere that we'll maintain 6.1 for 10 years.13:31
jkiat least not for a general-purpose LTS13:31
pave1That will likely not change anything.13:31
jki...working towards13:31
jkiright13:31
jkiwe need a gap analysis13:31
jkiand then we could also discuss with potential other stakeholders13:32
patersonc[m]Having LTS back at 2 years would likely lead to more users of CIP. We just need to convert some of those users to paying members so we can fund the maintenance :)13:32
jkior ask Greg with whome he already talked13:32
pave1Then we should probably go through our channels at LF to see what would be required.13:32
pave1Both -stable and -cip are lf projects after all.13:32
jkiis stable a formal project?13:33
jkior "just" a task of Greg?13:33
pave1Not sure really.13:33
pave1Talk to Neil C. if we don't get results from public discussion>13:34
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)13:34
jkiso, back to that public thread to start - where, how, who?13:35
pave1Also maybe Siemens / Renesas could publicly explain that -lts is important?13:35
jkisure, that can be done13:35
jkipavel: would you like to start a discussion? or should I?13:37
pave1Not sure, this level of management is over my usual levels...13:37
pave1jki -- I'd be happy if you would.13:37
jkiwho has talked most to him so far? that was my idea behind it13:37
jkiI didn't do much in LTS context, but can try if there is no better fit13:38
jkigreat, so I generated an AI for me :)13:39
jkibut I will take you in CC-custody!13:40
pave1I'm usually the one replying to stable announcements, but that is 'engineering' level13:40
pave1and I believe we are talking more management level here.13:40
patersonc[m]Thank you jki !13:41
jkipatersonc[m]: can you organize that someone from Renesas will be able to follow-up with needs and use-case on that?13:41
jkiI can make a start for Siemens as part of the email13:42
pave1I can talk to SuSE if they have any long-term plans  for 6.1.13:42
jkipavel: TIA!13:42
jkiother members would be good to see on stage then, too13:43
patersonc[m]jki: Sure13:43
patersonc[m]I guess it's the general use case behind CIP :)13:43
pave1Probably could ask RedHat too, but  maybe someone has better contacts there.13:44
jkiyes, but it is stronger if there are mutliple voice with some concrete cases13:44
jkiwho all contributed to stable so far?13:44
jkiLinaro seems to be out13:44
jkiYocto?13:44
pave113:47
jkiand who to contact on Debian side? i suppose iwamatsu-san has contacts there13:48
patersonc[m]yea13:49
pave1I guess so.13:49
jkiit still appears to me that Debian could be our strongest ally on this, also use case wise13:50
pave1I have very little idea how Debian works with kernel.13:51
jkiit seems to me they have very few core people to integration / port, and then the community as test lab13:52
pave1Actually.. someone does Debian lts maintainance 'for hire'.13:53
jkianyway, I'll ask iwamatsu, maybe also try to reach ben on this13:53
jkisure, we pay them as well13:53
pave1Those might be good people to talk to.13:53
jkibut I don't know which persons of the lts team do kernel, and how many13:54
pave1They probably do little lts kernel development, but it is likely important to them and their customers.13:55
jkiraphael hertzog...13:55
jkiwill try that direction too13:55
jkiany other ideas / thoughts?13:57
jkior even other AOBs?13:57
patersonc[m]The kernel sources things13:58
patersonc[m]s/things/thing/13:58
jkiplease go ahead!13:58
patersonc[m]In older kernel versions, in cip-kernel-config we had a script that went through and generated .sources files13:58
patersonc[m]This hasn't been done for 5.1013:58
patersonc[m]I wondered if this approach is still used?13:58
patersonc[m]My understanding is that these .sources files were somehow used to track what we needed to maintain in the kernel - I could be wrong of course...13:59
pave1Probably still used, probably someone just needs to run the scripts.14:00
pave1Likely iwamatsu as he is maintaining configs repository.14:00
jkithen ask again next week or via the ML?14:00
*** sietze <sietze!~sietze_va@msw-v.fe.bosch.de> has quit IRC (Quit: Leaving)14:01
pave1I guess ML is best.14:01
jkipatersonc[m]: next AI for you ;)14:01
patersonc[m]Ha14:01
jkianything else for today?14:02
patersonc[m]Not from me14:02
jki514:03
jki414:03
jki314:03
jki214:03
jki114:03
jki#endmeeting14:03
collab-meetbot`Meeting ended Thu Mar  2 14:03:16 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:03
collab-meetbot`Minutes:        http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-02-13.03.html14:03
collab-meetbot`Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-02-13.03.txt14:03
collab-meetbot`Log:            http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/03/cip.2023-03-02-13.03.log.html14:03
*** 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/"14:03
jkithank you all!14:03
pave1Thank you!14:03
ulithanks14:03
masamithanks14:03
*** masami <masami!~masami@FL1-125-198-44-131.tky.mesh.ad.jp> has quit IRC (Quit: Leaving)14:03
alicefmthanks14:03
*** fbezdeka <fbezdeka!~flo@2a02:810d:8780:7fc:b0:fb65:f05a:7717> has left #cip14:04
*** jki <jki!~jki@165.225.26.243> has quit IRC (Quit: Leaving)14:05
*** uli <uli!~uli@195.52.139.214> has left #cip (Leaving)14:05
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip14:21
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)16:46
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip20:23
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 248 seconds)22:44
« Wednesday, 2023-03-01 Index Friday, 2023-03-03 »

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