fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

11K
active users

Seems I need to be more careful what I write here, as it seems one of my sneaky remarks lead to a patch. 😂

powerpc/boot: Remove bogus reference to lore.kernel.org/all/2024100905

From @mpe – and according to the Link tag triggered by fosstodon.org/@kernellogger/11 (see Screenshot)

@kernellogger @mpe or, maybe you should be less careful in order to generate more kernel patches 😆

Petr Tesarik

@Aissen @kernellogger @mpe Thorsten, we're all hanging on your lips, ready to make patches like crazy!

@ptesarik @Aissen @mpe

Patches, hah, who wants those -- they sooner or later will come about anyway when a problem hits someone's nerve.

Help fixing all those development process issues that lead to regressions and others problems is what I could need. 😟 🥴 😬

@ptesarik @Aissen @mpe

> Thorsten, we're all hanging on your lips, ready to make patches like crazy!

Be careful what you say, otherwise I might follow your advice. 😬 🙃

I was tempted a few hours ago -- but quickly decided submitting a rough patch myself is the way better approach. 😄

See lore.kernel.org/all/42aa307d7f or fosstodon.org/@kernellogger/11 for details.

lore.kernel.org[RFC PATCH v1] module: sign with sha512 by default to avoid build errors - Thorsten Leemhuis

@ljs @mpe @ptesarik @Aissen

"he's gone rogue" really is the right description here, as the "I don't know what I'm doing [...]" section in the comment to the patch shows… 😄

@kernellogger @ljs @mpe @ptesarik @Aissen Soon we get to report regressions against the regression tracker yehaaw 🤠

@kernellogger @ptesarik @Aissen @mpe You can also add "default MODULE_SIG_SHA256" or whatever to the "choice" section above it so you don't have an implicit dependency on the ordering.

@kernellogger @vegard MODULE_SIG_HASH is not a choice, it's a string that is set based on which of the MODULE_SIG_SHAxxx options was selected above. You shouldn't need to touch that section.

Adding `default MODULE_SIG_SHA512` to the choice (~line 234) should do it.

@mpe @vegard

thx, yeah, it does – but then all the other CONFIG_MODULE_SIG_SHA* options are disabled in an allmodconfig config; maybe nobody cares, but it *feels* like I'm breaking some "let's ensure all the algorithms are built in a allmodconfig build" trickery someone created on purpose

@kernellogger @vegard

I don't think that's a problem.

Only one of the MODULE_SIG_SHAxxx options can ever be enabled at a time - because they're inside a `choice`.

More than one *algorithm* can still be enabled, but those are the CRYPTO_SHAxxx symbols, not the MODULE_SIG_SHAxxx ones.

@mpe @vegard

hah, of course, you are right, sorry, I was missing the obvious!