On Tue Mar 31, 2026 at 10:54 AM CEST, Anil Dongare -X (adongare - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote: > Hi Yoann, > > Thank you for the detailed explanation! That makes perfect sense now. I > misunderstood and was looking at the source code indentation rather than the > unified diff format itself. I clearly see now via cat -t that the context > line indicator was a tab instead of a space. > > I will regenerate the patch properly (I'll look into using devtool as you > recommended) and send out an updated version. > > Going forward, besides manually checking the diff, is there a specific script > or tool (like a patch checker) you recommend using to verify the patch format > is strictly correct before sending it to the mailing list?
I don't know of any. I just noticed it because I've setup my text editor to display whitespaces (but that's mostly luck). Maybe check your next patches with a trivial regexp? grep '^\t' xxx.patch and review output? > Thanks again for your patience and help! > > Best regards, Anil Regards, -- Yoann Congal Smile ECS
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#234282): https://lists.openembedded.org/g/openembedded-core/message/234282 Mute This Topic: https://lists.openembedded.org/mt/118257283/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
