| *** monstr <monstr!~monstr@nat-35.starnet.cz> has joined #cip | 06:51 | |
| *** monstr <monstr!~monstr@nat-35.starnet.cz> has quit IRC (Ping timeout: 252 seconds) | 07:04 | |
| *** sashal <sashal!sid491190@id-491190.hampstead.irccloud.com> has quit IRC (Read error: Connection reset by peer) | 12:14 | |
| *** sashal <sashal!sid491190@id-491190.hampstead.irccloud.com> has joined #cip | 12:15 | |
| *** jki <jki!~jki@62.156.206.17> has joined #cip | 12:57 | |
| *** masami <masami!~masami@FL1-122-135-239-77.tky.mesh.ad.jp> has joined #cip | 12:58 | |
| arisut | hi | 12:59 |
|---|---|---|
| jki | hi! | 12:59 |
| uli_ | hello | 13:00 |
| masami | hello | 13:00 |
| pave1 | hi! | 13:00 |
| jki | ok, let's start | 13:01 |
| jki | #startmeeting CIP IRC weekly meeting | 13:01 |
| collab-meetbot` | Meeting started Thu Mar 13 13:01:22 2025 UTC and is due to finish in 60 minutes. The chair is jki. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:01 |
| collab-meetbot` | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
| collab-meetbot` | The meeting name has been set to 'cip_irc_weekly_meeting' | 13:01 |
| *** collab-meetbot` changes topic to " (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | #topic AI review | 13:01 |
| *** collab-meetbot` changes topic to "AI review (Meeting topic: CIP IRC weekly meeting)" | 13:01 | |
| jki | - share release scripts/procedures [pavel, iwamatsu-san] | 13:01 |
| jki | any news here? | 13:01 |
| pave1 | sent email to cip-dev :-) | 13:02 |
| jki | ah, just saw it | 13:02 |
| jki | ok, now nobuhiro needs to share as well, and then you can sync | 13:02 |
| pave1 | I can put procedures into bin/ as text file into the repository, if that helps. | 13:02 |
| jki | let's look at it again next time | 13:02 |
| jki | you can suggest that along your posting, but all maintainers should have a chance to comment | 13:03 |
| pave1 | yep, no problem. | 13:03 |
| arisut | thanks :) | 13:03 |
| jki | ok, that was the only AI I had recorded | 13:04 |
| jki | 5 | 13:04 |
| jki | 4 | 13:04 |
| jki | 3 | 13:04 |
| jki | 2 | 13:04 |
| jki | 1 | 13:04 |
| jki | #topic Kernel maintenance updates | 13:04 |
| *** collab-meetbot` changes topic to "Kernel maintenance updates (Meeting topic: CIP IRC weekly meeting)" | 13:04 | |
| masami | This week reported 82 new CVEs and 15 updated CVEs. | 13:04 |
| uli_ | i released 4.19, now working on 4.4 | 13:04 |
| jki | nobuhiro: "I am reviewing 6.1.130." | 13:05 |
| pave1 | I'm reviewing 6.1.131 and .130. Big patch from Renesas landed. | 13:05 |
| pave1 | ...in the inbox, 85 patches in series. | 13:05 |
| jki | that's more than what is generally recommended... | 13:07 |
| pave1 | Yep, its new hardware support. | 13:07 |
| jki | still it might be splittable | 13:08 |
| pave1 | Not sure in this case. I'll take a look, if it has impact | 13:09 |
| jki | ok | 13:09 |
| pave1 | on non-renesas code, I'll push back. | 13:09 |
| jki | other maintenance topics? | 13:09 |
| jki | 5 | 13:10 |
| jki | 4 | 13:10 |
| jki | 3 | 13:10 |
| jki | 2 | 13:10 |
| jki | 1 | 13:10 |
| jki | #topic Kernel release status | 13:10 |
| *** collab-meetbot` changes topic to "Kernel release status (Meeting topic: CIP IRC weekly meeting)" | 13:10 | |
| jki | all on track, but quite a few are due early next week | 13:10 |
| pave1 | Yes. Including first self-maintained 4.19-rt. | 13:10 |
| jki | :) | 13:11 |
| jki | anything to add? | 13:12 |
| jki | 5 | 13:12 |
| jki | 4 | 13:12 |
| jki | 3 | 13:12 |
| jki | 2 | 13:12 |
| jki | 1 | 13:13 |
| jki | #topic Kernel testing | 13:13 |
| *** collab-meetbot` changes topic to "Kernel testing (Meeting topic: CIP IRC weekly meeting)" | 13:13 | |
| arisut | currently working on adding CIP configurations to KernelCI | 13:13 |
| patersonc | Thank you arisut | 13:13 |
| patersonc | I'm testing a LAVA MR in my local lab, now that I've got it working again. | 13:14 |
| patersonc | Not much other news atm | 13:15 |
| jki | anything else on testing | 13:16 |
| jki | ? | 13:16 |
| jki | 5 | 13:17 |
| jki | 4 | 13:17 |
| jki | 3 | 13:17 |
| jki | 2 | 13:17 |
| jki | 1 | 13:17 |
| jki | #topic AOB | 13:17 |
| *** collab-meetbot` changes topic to "AOB (Meeting topic: CIP IRC weekly meeting)" | 13:17 | |
| pave1 | Mailing list is corrupting From. That breaks DCO and prevents direct replies. | 13:17 |
| pave1 | Not ok by me. | 13:17 |
| jki | already replied | 13:17 |
| jki | please provide examples | 13:17 |
| jki | didn't notice this yet, also while picking up patches for isar-cip-core from the list | 13:18 |
| pave1 | Date: Thu, 13 Mar 2025 13:34:50 +0100 | 13:18 |
| pave1 | From: "Pavel Machek via lists.cip-project.org" <pavel=denx.de@lists.cip-project.org> | 13:18 |
| jki | link pleaes | 13:18 |
| pave1 | Hmm, I wander what is going on there. | 13:19 |
| pave1 | Your reply does not have [cip-dev] in the subject, so you was replying to direct copy I was sending to you. | 13:19 |
| jki | that's DKIM | 13:19 |
| patersonc | I know what you mean Pavel - I find it annoying too. If I reply to your email it'll go to the mailing list, not you personally. | 13:20 |
| jki | nope, I replied to the email from nntp.lore.kernel.org | 13:20 |
| pave1 | DKIM? | 13:20 |
| jki | https://de.wikipedia.org/wiki/DomainKeys_Identified_Mail | 13:21 |
| pave1 | Ok, so every email I get from the list has mangled From. It means I can reply privately. | 13:21 |
| pave1 | Not sure what is different in your setup. | 13:21 |
| jki | that's why it is highly recommended to start your patch content with "From: my real <address>" | 13:22 |
| jki | still, it is not done by all senders, and I do have issues picking up patches from the list nevertheless | 13:23 |
| jki | from direct posting or via nntp | 13:23 |
| pave1 | Well, all emails are not patches, and other mailing lists do not behave like that. | 13:24 |
| patersonc | Do all groups.io ML have the same issue? Or is it a settings thing for our ML? | 13:24 |
| jki | anyway, please cite concrete cases | 13:24 |
| pave1 | I worry that someone will save my mangled email adress. | 13:24 |
| jki | then we can forward them | 13:24 |
| pave1 | Ok, I was kind of hoping list owner would explain. | 13:24 |
| jki | they are all archived on the lore.kernel.org | 13:25 |
| jki | list owner is most likely not following your public list in such details | 13:25 |
| pave1 | So who to contact? | 13:26 |
| pave1 | Everything I get from the mailing list has mangled addresses. Including emails from you. | 13:26 |
| jki | I can forward that to Regina, but I need concrete examples | 13:27 |
| pave1 | I don't know what other people see in their inboxes, but patersonc sees it too, and I'm fairly sure it is not my system doing that. | 13:27 |
| uli_ | +1 | 13:27 |
| jki | our inbox should see what lore.kernel.org recorded | 13:28 |
| jki | anything else is hard to tell apart from local server or client issues | 13:28 |
| pave1 | That's not the case. lore has unmangled version. | 13:28 |
| pave1 | And I can't get raw email from https://lists.cip-project.org/g/cip-dev/message/18189 | 13:30 |
| jki | that is the broken groups.io interface, not useful for such things | 13:31 |
| pave1 | Are you subscribed to the list, and receiveing messages over smtp to siemens server? | 13:32 |
| jki | nope, I usually avoid subscriptions or silence them | 13:33 |
| jki | nntp polling preferred | 13:33 |
| pave1 | Aha, so that's the difference. I'm subscribed, so the messages go over smtp to our mail serivce. | 13:33 |
| jki | maybe LF disabled DKIM when formwarding to lore.kernel.org, and that's why we don't see it there | 13:34 |
| jki | and in nntp | 13:35 |
| jki | https://lists.cip-project.org/g/cip-dev/original/18189 is also not fully reporting addresses | 13:35 |
| jki | patchwork.kernel.org should be fine as well | 13:35 |
| jki | and would be another source for retrieving unmangled patches | 13:36 |
| patersonc | Yea patchwork seems to be okay: https://patchwork.kernel.org/project/cip-dev/patch/20250313054155.337079-1-badrikesh.prusty@siemens.com/ | 13:37 |
| patersonc | Still not ideal though - it would be nice to be able to hit reply in a mail client and for it to work | 13:37 |
| jki | that normally works because of "reply-to" | 13:38 |
| jki | even on dkim mangled lists | 13:38 |
| pave1 | Reply-to is set to the list: | 13:39 |
| pave1 | Reply to cip-dev@lists.cip-project.org? ([yes]/no): | 13:39 |
| jki | hmm, that is suboptimal, indeed | 13:39 |
| pave1 | So if I do yes it goes to everyone, if I say No it goes to To: "Jan Kiszka via lists.cip-project.org" <jan.kiszka=siemens.com@lists.cip-project.org> | 13:39 |
| pave1 | Ok, lets see if someone has idea on the list, and if not we can talk about it next week? | 13:40 |
| patersonc | It looks like there is a setting for that in groups.io. I've just set the cip-testing-results ML to be "reply to sender and group". Now it does exactly that. Maybe we can set the same for the cip-dev ML? | 13:40 |
| patersonc | It still scrw | 13:40 |
| jki | this is the other key word about this: DMARC https://en.wikipedia.org/wiki/DMARC | 13:40 |
| jki | some list hosts to that, have to do that, other likel kernel.org seem to avoid it or have found workarounds | 13:41 |
| jki | googlegroups does DMARC but set the sender in reply-to | 13:42 |
| pave1 | That would be improvement, yes. | 13:43 |
| jki | anyway, all that is nothing new, commonly in place for 5 years or so in many spots | 13:43 |
| jki | I'll ask Regina if she or LF support can tune "reply-to" | 13:44 |
| pave1 | Thank you! | 13:44 |
| pave1 | 6.12 branch. | 13:44 |
| jki | ok | 13:44 |
| jki | I have one topic for next week: | 13:44 |
| jki | I might be blocked for the meeting, not 100% clear yet | 13:45 |
| jki | who could jump in if needed? | 13:45 |
| pave1 | I can take over if you are not here by 13utc? :-) | 13:46 |
| pave1 | Or set your own deadline :-). | 13:46 |
| jki | TIA! | 13:46 |
| jki | 13:01 UTC ;) | 13:46 |
| pave1 | ok :-). | 13:46 |
| jki | anything else for today? | 13:46 |
| pave1 | 6.12 branch | 13:46 |
| jki | yes | 13:46 |
| jki | where are we? | 13:47 |
| pave1 | I can do the scheduled -rt releases and then branch it from 6.12.18 or 6.12.19, whatever is available at the time? | 13:47 |
| pave1 | Or do I make it a priority? | 13:48 |
| jki | I would say the regular releases are more important | 13:48 |
| jki | we don't have hundreds of patches for 6.12-cip waiting | 13:48 |
| jki | yet :) | 13:48 |
| pave1 | Just 85 :-). | 13:48 |
| pave1 | Ok, plan is clear, thanks! | 13:49 |
| jki | good | 13:50 |
| jki | further topics? | 13:50 |
| jki | 5 | 13:50 |
| jki | 4 | 13:50 |
| jki | 3 | 13:50 |
| jki | 2 | 13:50 |
| jki | 1 | 13:50 |
| jki | #endmeeting | 13:50 |
| collab-meetbot` | Meeting ended Thu Mar 13 13:50:54 2025 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/2025/03/cip.2025-03-13-13.01.html | 13:50 |
| collab-meetbot` | Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-13-13.01.txt | 13:50 |
| collab-meetbot` | Log: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-13-13.01.log.html | 13: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 | |
| jki | thanks all! | 13:50 |
| uli_ | thanks | 13:51 |
| arisut | thx | 13:51 |
| masami | thank you | 13:51 |
| *** masami <masami!~masami@FL1-122-135-239-77.tky.mesh.ad.jp> has quit IRC (Quit: Leaving) | 13:51 | |
| patersonc | Cheers | 13:51 |
| pave1 | Thank you! | 13:51 |
| *** jki <jki!~jki@62.156.206.17> has quit IRC (Remote host closed the connection) | 13:53 | |
| pave1 | ;2~ | 13:58 |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Ping timeout: 248 seconds) | 20:52 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has joined #cip | 20:52 | |
| *** prabhakalad <prabhakalad!~prabhakar@165.225.17.42> has quit IRC (Ping timeout: 245 seconds) | 21:48 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!