*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Ping timeout: 246 seconds) | 01:37 | |
*** prabhakar <prabhakar!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Ping timeout (120 seconds)) | 03:17 | |
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has joined #cip | 05:59 | |
*** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:15 | |
*** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 248 seconds) | 06:20 | |
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #cip | 07:32 | |
*** frieder <frieder!~frieder@i4DF677E2.static.tripleplugandplay.com> has joined #cip | 10:30 | |
*** uli <uli!~uli@2001:4090:a246:82be:c346:305b:de9b:ba3> has joined #cip | 11:31 | |
*** masami <masami!~masami@FL1-211-135-148-63.tky.mesh.ad.jp> has joined #cip | 11:46 | |
*** jki <jki!~jki@62.156.206.14> has joined #cip | 11:56 | |
jki | hi everyone | 12:00 |
---|---|---|
pave1 | Hi! | 12:00 |
uli | hello | 12:00 |
masami | hi | 12:00 |
arisut_ | hi | 12:00 |
patersonc | Hello | 12:00 |
*** arisut_ is now known as arisut | 12:00 | |
jki | ok, let's go | 12:01 |
jki | #startmeeting CIP IRC weekly meeting | 12:01 |
collab-meetbot` | Meeting started Thu Aug 31 12:01:55 2023 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 12:01 |
collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 12:01 |
collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 12:01 |
*** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
jki | #topic AI review | 12:01 |
*** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 12:01 | |
jki | 1. create kernelci pipeline for buster images (arisut) | 12:02 |
arisut | jki: still didn't get replay to my email | 12:02 |
iwamatsu | hi all, | 12:02 |
jki | I thought I replied... | 12:02 |
arisut | https://lists.cip-project.org/g/cip-dev/message/12810 | 12:02 |
arisut | is the most recent one | 12:02 |
arisut | https://lists.cip-project.org/g/cip-dev/topic/100775400#12810 | 12:03 |
jki | ok, possibly misremembered, will follow up | 12:03 |
arisut | thanks | 12:03 |
jki | 2. draft press release about 6.1-cip (jan) | 12:03 |
jki | sent, seems the board still needs to do some decisions | 12:03 |
jki | thanks for your feedback already | 12:04 |
jki | any other AI I missed? | 12:04 |
jki | 3 | 12:04 |
jki | 2 | 12:04 |
pave1 | This should be everything. | 12:04 |
jki | 1 | 12:04 |
jki | #topic Kernel maintenance updates | 12:04 |
*** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 12:04 | |
masami | This week reported 4 new CVEs and 5 updated CVEs. | 12:04 |
uli | i'm preparing 4.4 for release and reviewing 6.1.46 | 12:05 |
pave1 | I did some reviews, 6.1.48 to 6.1.50. | 12:05 |
iwamatsu | I reviewed 6.1.46, 47, 48, 49, and I am reviewing 6.1.50. | 12:05 |
jki | some curious question on the review process: when you check patches for 6.1, do you also already check if they apply to older stable? | 12:07 |
jki | or is that done later? | 12:07 |
pave1 | Well, this is getting messy. | 12:07 |
pave1 | Greg used to publish his queues, so it was possibly to review patches before they were released. | 12:08 |
pave1 | He no longer does that. | 12:08 |
pave1 | Still, we try to group the patches by the "upstream commit" id, | 12:08 |
pave1 | and then review the version targeted for the oldest release. | 12:09 |
pave1 | So if the patch is queued for 4.14, 4.19, 5.10 and 6.1, we review 4.14 version. | 12:09 |
jki | did anyone talk to Greg about that? | 12:10 |
pave1 | I tried. | 12:10 |
pave1 | ...with not much success. He said he was not aware how those queue branches were generated. | 12:11 |
jki | ok | 12:11 |
jki | well, anything else on "maintenance"? | 12:12 |
jki | 5 | 12:12 |
jki | 4 | 12:12 |
jki | 3 | 12:12 |
jki | 2 | 12:12 |
jki | 1 | 12:12 |
jki | #topic Kernel release status | 12:12 |
*** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 12:12 | |
jki | 4.4 | 12:13 |
uli | on track, will send a request for reviews in the next few days | 12:13 |
pave1 | -rt should be on track. | 12:13 |
jki | 4.19 | 12:13 |
iwamatsu | on track | 12:13 |
jki | 5.10 | 12:13 |
iwamatsu | on track | 12:13 |
jki | sorry: RT for both as well? | 12:14 |
iwamatsu | yes | 12:14 |
jki | 6.1 | 12:14 |
pave1 | -rt trees should be on track, all of them. | 12:14 |
iwamatsu | on track | 12:14 |
jki | good | 12:14 |
jki | #topic Kernel testing | 12:14 |
*** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 12:14 | |
patersonc | Hello. | 12:15 |
patersonc | The Denx LAVA lab is now back online | 12:15 |
patersonc | So we'll have more devices online again | 12:15 |
patersonc | I had a quick look at your isar linux source download issue Jan and sent a commit for adding gitlab cache support | 12:16 |
patersonc | Feel free to give it a go | 12:16 |
patersonc | I've not much else this week | 12:16 |
jki | patersonc: where did you send that commit to? | 12:17 |
patersonc | cip-dev | 12:18 |
patersonc | https://gitlab.com/cip-project/cip-core/isar-cip-core/-/commit/c62fced2cd86757aa0eebc14eedf04c203f34cde | 12:18 |
patersonc | There's a completed pipeline there as well | 12:18 |
jki | didn't see it on the list yet, will check again | 12:19 |
patersonc | Okay :) | 12:19 |
jki | but caching will only help after the first re-run | 12:19 |
jki | it will cause failures after every kernel update | 12:20 |
jki | I'm not in favor of it therefore | 12:20 |
patersonc | There is that risk, yes | 12:20 |
patersonc | You could have an automated nightly build to download and save the relevant files to the cache | 12:21 |
jki | yes, and promote that pattern downstream | 12:21 |
jki | it remains a workaround IMHO | 12:21 |
patersonc | Yea, kernel.org should really be more stable :P | 12:21 |
jki | we will also check how many caches will be generated and if they will be shared | 12:22 |
patersonc | It depends on the key | 12:22 |
patersonc | If they use the same key it will be shared | 12:22 |
jki | will the caches accumulated the fetches? | 12:22 |
patersonc | Although the master branch usually has a different set - unless an option is changed | 12:22 |
jki | will they grow larger and larger therefore? | 12:23 |
jki | I'm afraid there are still many missing bits, even for this approach | 12:23 |
patersonc | Yes | 12:23 |
jki | ah, you didn't send a patch, you only provided that commit link in your reply | 12:24 |
patersonc | oh yea, sorry | 12:24 |
jki | we can start using caches, also sstate caches in fact, but that will need cache maintenance | 12:25 |
jki | given the increasing number of jobs, it may actually be benefical for our CI time | 12:25 |
jki | storage should still be much cheaper (will likely need to use S3 for that) | 12:25 |
jki | anyway - anything else on this? I'll follow up on the ML in any case | 12:27 |
patersonc | Nothing from me | 12:27 |
jki | anything else on testing in general? | 12:28 |
jki | 5 | 12:28 |
jki | 4 | 12:28 |
jki | 3 | 12:28 |
jki | 2 | 12:28 |
jki | 1 | 12:28 |
jki | #topic AOB | 12:29 |
*** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 12:29 | |
jki | anyone anything? | 12:30 |
jki | 5 | 12:31 |
jki | 4 | 12:31 |
jki | 3 | 12:31 |
jki | 2 | 12:31 |
jki | 1 | 12:31 |
jki | #endmeeting | 12:31 |
collab-meetbot` | Meeting ended Thu Aug 31 12:31:12 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 12:31 |
collab-meetbot` | Minutes: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/08/cip.2023-08-31-12.01.html | 12:31 |
collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/08/cip.2023-08-31-12.01.txt | 12:31 |
collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2023/08/cip.2023-08-31-12.01.log.html | 12:31 |
*** 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:31 | |
jki | thank you all! | 12:31 |
iwamatsu | thank you | 12:31 |
uli | thanks | 12:31 |
masami | thank you | 12:31 |
pave1 | Thank you! | 12:31 |
patersonc | Cheers all | 12:31 |
*** masami <masami!~masami@FL1-211-135-148-63.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 12:31 | |
*** jki <jki!~jki@62.156.206.14> has quit IRC (Remote host closed the connection) | 12:34 | |
arisut | thanks | 12:35 |
*** uli <uli!~uli@2001:4090:a246:82be:c346:305b:de9b:ba3> has left #cip (Leaving) | 15:10 | |
*** frieder <frieder!~frieder@i4DF677E2.static.tripleplugandplay.com> has quit IRC (Remote host closed the connection) | 15:59 | |
*** Guest97 <Guest97!~Guest34@197.87.144.233> has joined #cip | 16:28 | |
Guest97 | hi, I want compile the 4.4 kernel on debian 9 | 16:28 |
Guest97 | In a fresh debian 9 I ran this: git clone --single-branch --depth=1 -b linux-4.4.y-cip https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git | 16:28 |
Guest97 | then did a make all, but I get this error | 16:29 |
Guest97 | net/decnet/dn_neigh.c:74:9: error: implicit declaration of function ‘neigh_key_eq16’ [-Werror=implicit-function-declaration] | 16:29 |
Guest97 | return neigh_key_eq16(neigh, pkey); | 16:29 |
Guest97 | any advice if I am getting the sources incorrectly and/or how I should be compiling cip 4.4 | 16:29 |
Guest97 | I noticed this commit removes the function: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/?h=linux-4.4.y-cip&id=cd94d54fbf8f04204b0d8e8da6a13d9c94f108b5 | 16:32 |
Guest97 | should I be using a tag such as "v4.4-st42" maybe? | 16:34 |
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 17:03 | |
*** Guest97 <Guest97!~Guest34@197.87.144.233> has quit IRC (Quit: Client closed) | 17:09 | |
arnd | Guest97: if that's the only error you get, you can probably just turn off decnet, it's very unlikely to be needed | 17:10 |
*** rajm <rajm!~robert@cpc126990-macc4-2-0-cust43.1-3.cable.virginm.net> has quit IRC (Ping timeout: 245 seconds) | 21:46 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!