Kernel Recipes is very soonβ’; if we meet and you want a Rust for Linux sticker, just ask me ! (Courtesy of Miguel Ojeda) @KernelRecipes
#KernelRecipes
Linux Plumbers in-person tickets are sold out! But you can still add yourself to the wait-list. Read the blog for more details. https://lpc.events/blog/current/index.php/2025/09/19/in-person-registration-is-sold-out-2/
Registration for LPC 2025 is now open!
Please refer to our latest blog post for more details.
https://lpc.events/blog/current/index.php/2025/09/15/registration-for-lpc-2025-is-now-open/
Linux Plumbers 2025 in Tokyoβs Call for Proposals is nearing its end! https://lpc.events/blog/current/index.php/2025/09/08/the-call-for-proposals-is-nearing-its-end/
Upcoming deadline alert!
September 10th is the deadline to submit your proposal to LPC referred track and the Kernel Summit track. If you have something to share, please submit your proposal ASAP!
For more details of all the deadlines, please refer to our latest blog post.
https://lpc.events/blog/current/index.php/2025/09/08/the-call-for-proposals-is-nearing-its-end/
@krzk @kernellogger @geert I have something for this: https://git.kernel.org/pub/scm/linux/kernel/git/vegard/linux.git/about/
It's basically cross-referencing lore and git (and a bunch of other stuff like CVEs, stable, syzbot links, etc.) and adding the links as git notes (displayed after the changelog). There's obviously a delay between the data being available and it actually updating. I haven't been updating it very often but I would if there were actual users.
After missing the last one due to a sick kiddo, I'm excited the next PDX Linux Kernel Meetup is scheduled for Sept 18th!
Hope to see folks there!
https://ikluft.github.io/pdx-lkmu/september-2025-portland-linux-kernel-meetup.html
#Linux 6.17-rc5 is out:
https://lore.kernel.org/lkml/CAHk-=wh5AyuvEhNY9a57v-vwyr7EkPVRUKMPwj92yF_K0dJHVg@mail.gmail.com/
""Things remain normal - both the diffstat and the commit counts look entirely sane. [β¦]
The one discussion that I was part of that happened last week that might be worth mentioning is that I've been complaining for years about useless "Link:" entries in commit messages that don't point to any new information. [β¦] if that link ends up being just a pointer to the email that became that commit - with nothing else - that allegedly helpful link only added human cost for me.
The same ends up being true when chasing down bug reports.
So please: don't add useless information to commits in general, but in _particular_ don't add "Link:" tags that only point back to the original submission email. [β¦]
Make the links be something *useful*. Make them point to the report for the bug that was the cause of the commit. Make them point to the discussion that explains the impetus for the commit. [β¦]
Make "Link:" tags be something to celebrate, not something to curse because they are worthless and waste peoples time.
Please?
Linus""
The video of my presentation at OSSummit Europe is now available. π³π±π§
Those were 180 slides in 40 mins. π«£π I hope people find it useful. Thanks! π
Abstract & slides in the comments.
Linux Kernel Self-Protection Project π§π‘βοΈ
#OSSummit #Linux #OpenSource