lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <trinity-c4c6b25b-8372-453e-b5e5-5d4003282d7c-1696068689143@3c-app-mailcom-bs15>
Date:   Sat, 30 Sep 2023 12:11:29 +0200
From:   daggs <daggs@....com>
To:     linux-kernel@...r.kernel.org
Subject: question regarding coding convention

Greetings,

I have a question regarding the kernel coding convention.
lets say I want to add a new arch named foo and there is a func named goo which all other archs are implementing but foo isn't.
what is the proper way to handle it? as the kernel code is quite big, I didn't found any example.

Thanks,

Dagg

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ