On Fri, Jan 23, 2026 at 4:38 AM Mikko Rapeli <[email protected]> wrote:
> On Fri, Jan 09, 2026 at 11:23:41AM -0500, Bruce Ashfield wrote: > > On Fri, Jan 9, 2026 at 10:35 AM Mikko Rapeli <[email protected]> > > wrote: > > > > > These are hidden behind CRYPTO_USER_API_ENABLE_OBSOLETE which > > > is not set. Found by new merge_config.sh which checks for > > > merged vs. effective configs. > > > > > > > But other stacks may set that, and then include the fragment. So as long > > as they are valid options in the kernel, and reachable by some means, > > they can stay in the fragment. > > Which stacks do you mean? CRYPTO_USER_API_ENABLE_OBSOLETE is only used > by cfg/crypto-obsolete-disable.scc to set it off to =n. > > If someone outside of yocto-kernel-cache sets > CRYPTO_USER_API_ENABLE_OBSOLETE=y then I think they should also enable the > wanted obsolete crypto libraries explicitly. I don't think > ktypes/standard/standard.cfg should be setting obsolete config options > when they are effectively disabled in all settings used by the oe-core > repository kernel configs. > We can think that, but we can't mandate it. I'll add some depreciation warnings around these, but if they are setting that option, and then including the fragment these options need to be available and can't silently disappear They aren't doing any harm being enabled (and by that I mean runtime or similar other issues) (they could be shuffled into another fragment vs dropped, but then there's a discovery question). Given the reality that I don't have visibility into everyone's configuration stacks, I error on the side of keeping things around. That goes along with what I was saying in other comments, that the design decision is that the fragments are as generally useful as possible versus being completely standalone and non-overlapping. The patch is still useful though, as I'll now get them onto the warn-if-used list and that gets them on the way out. Bruce > > To me this kind of cleanup is expected and downstream users just need to > adapt since kernel config has moved forward and certain options really > are obsolete and should not be used. > > Cheers, > > -Mikko > > > Bruce > > > > > > > > > > > > Signed-off-by: Mikko Rapeli <[email protected]> > > > --- > > > ktypes/standard/standard.cfg | 4 ---- > > > 1 file changed, 4 deletions(-) > > > > > > diff --git a/ktypes/standard/standard.cfg > b/ktypes/standard/standard.cfg > > > index 99fd01b67c8a..5b75bf5e38a6 100644 > > > --- a/ktypes/standard/standard.cfg > > > +++ b/ktypes/standard/standard.cfg > > > @@ -1078,10 +1078,6 @@ CONFIG_CRYPTO_SERPENT=m > > > CONFIG_CRYPTO_AES=y > > > CONFIG_CRYPTO_CAST5=m > > > CONFIG_CRYPTO_CAST6=m > > > -CONFIG_CRYPTO_TEA=m > > > -CONFIG_CRYPTO_ARC4=y > > > -CONFIG_CRYPTO_KHAZAD=m > > > -CONFIG_CRYPTO_ANUBIS=m > > > CONFIG_CRYPTO_DEFLATE=y > > > CONFIG_CRYPTO_MICHAEL_MIC=m > > > CONFIG_CRYPTO_CRC32C=y > > > -- > > > 2.34.1 > > > > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee > > at its end > > - "Use the force Harry" - Gandalf, Star Trek II > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16203): https://lists.yoctoproject.org/g/linux-yocto/message/16203 Mute This Topic: https://lists.yoctoproject.org/mt/117176754/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
