linux-kernel - Re: Referencing non-public datasheets in commit messages (was: [PATCH v12 3/3] EDAC: nuvoton: Add NPCM memory controller driver)

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <YvIRusXsZvdiFRzS@zn.tnic>
Date:   Tue, 9 Aug 2022 09:50:18 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Paul Menzel <pmenzel@...gen.mpg.de>
Cc:     medadyoung@...il.com, KWLIU@...oton.com, tony.luck@...el.com,
        rric@...nel.org, benjaminfair@...gle.com,
        linux-edac@...r.kernel.org, KFTING@...oton.com,
        avifishman70@...il.com, venture@...gle.com,
        openbmc@...ts.ozlabs.org, JJLIU0@...oton.com, ctcchien@...oton.com,
        tali.perry1@...il.com, devicetree@...r.kernel.org,
        robh+dt@...nel.org, james.morse@....com, YSCHU@...oton.com,
        mchehab@...nel.org, linux-kernel@...r.kernel.org,
        tmaimon77@...il.com
Subject: Re: Referencing non-public datasheets in commit messages (was:
 [PATCH v12 3/3] EDAC: nuvoton: Add NPCM memory controller driver)

On Tue, Aug 09, 2022 at 08:42:29AM +0200, Paul Menzel wrote:
> Maybe it could be denoted, that is not public (and also the version), but
> even mentioning non-public datasheets is useful, as they could be made
> public in the future, and allows everyone to contact people with access to
> these datasheets to take a look into the specific datasheet.

If you're going to contact people to get you certain information, you
don't need the datasheet - you simply need to ask the question.

But whatever, if a document is mentioned, the text should state that it
is not public so that people are aware not to go looking for it. Or, if
it is public, how to find it.

And no, a company website URL is not a good idea because those change
pretty frequently in practice. Uploading to our bugzilla and adding the
link to it is much better.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette