From: Borislav Petkov <bp@alien8.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: medadyoung@gmail.com, KWLIU@nuvoton.com, tony.luck@intel.com,
rric@kernel.org, benjaminfair@google.com,
linux-edac@vger.kernel.org, KFTING@nuvoton.com,
avifishman70@gmail.com, venture@google.com,
openbmc@lists.ozlabs.org, JJLIU0@nuvoton.com,
ctcchien@nuvoton.com, tali.perry1@gmail.com,
devicetree@vger.kernel.org, robh+dt@kernel.org,
james.morse@arm.com, YSCHU@nuvoton.com, mchehab@kernel.org,
linux-kernel@vger.kernel.org, tmaimon77@gmail.com
Subject: Re: Referencing non-public datasheets in commit messages (was: [PATCH v12 3/3] EDAC: nuvoton: Add NPCM memory controller driver)
Date: Tue, 9 Aug 2022 09:50:18 +0200 [thread overview]
Message-ID: <YvIRusXsZvdiFRzS@zn.tnic> (raw)
In-Reply-To: <6d1576c9-f105-2aff-4497-2c2e7bed2f3b@molgen.mpg.de>
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
prev parent reply other threads:[~2022-08-09 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 8:43 [PATCH v12 0/3] EDAC: nuvoton: Add nuvoton NPCM memory controller driver medadyoung
2022-06-10 8:43 ` [PATCH v12 1/3] dt-bindings: edac: nuvoton: add NPCM memory controller medadyoung
2022-06-20 16:40 ` Borislav Petkov
2022-08-08 6:40 ` Medad Young
2022-08-09 0:58 ` Kun-Fa Lin
2022-06-10 8:43 ` [PATCH v12 2/3] ARM: dts: nuvoton: Add memory controller node medadyoung
2022-06-20 17:29 ` Borislav Petkov
2022-06-10 8:43 ` [PATCH v12 3/3] EDAC: nuvoton: Add NPCM memory controller driver medadyoung
2022-06-20 19:20 ` Borislav Petkov
2022-08-09 6:42 ` Referencing non-public datasheets in commit messages (was: [PATCH v12 3/3] EDAC: nuvoton: Add NPCM memory controller driver) Paul Menzel
2022-08-09 7:50 ` Borislav Petkov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YvIRusXsZvdiFRzS@zn.tnic \
--to=bp@alien8.de \
--cc=JJLIU0@nuvoton.com \
--cc=KFTING@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=YSCHU@nuvoton.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=ctcchien@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=medadyoung@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robh+dt@kernel.org \
--cc=rric@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=tony.luck@intel.com \
--cc=venture@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).