On Fri, 2024-01-05 at 12:42 +0100, Alexander Kanavin wrote: > On Fri, 5 Jan 2024 at 12:22, Richard Purdie > <[email protected]> wrote: > > > I've a few ideas on how we might be able to detect potential problems, > > I'll continue to try and work something out but I want to make it clear > > there are some things it is hard to change :/. > > There's the option of adding another function (find_siginfo_v2) and > leaving this one as it was, this is how the kernel does things. They > don't shy away from adding v3, v4 and so on either. But I thought less > code is better than more code.
That is effectively what I just merged, except I did break compatibility by dropping the v1. We need to give the user good messages about how to fix their problem which is why a number is needed rather than just a function name. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#193354): https://lists.openembedded.org/g/openembedded-core/message/193354 Mute This Topic: https://lists.openembedded.org/mt/103239349/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
