From: Michael Richardson <mcr@sandelman.ca>
To: openbmc@lists.ozlabs.org
Subject: Re: Referencing non-public datasheets in commit messages (was: [PATCH v12 3/3] EDAC: nuvoton: Add NPCM memory controller driver)
Date: Tue, 09 Aug 2022 09:16:52 -0400 [thread overview]
Message-ID: <28431.1660051012@localhost> (raw)
In-Reply-To: <6d1576c9-f105-2aff-4497-2c2e7bed2f3b@molgen.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
If I need the datasheet, and I need to sign an NDA for it, then it's really
useful if I know *precisely* which datasheet I want, and to be sure that the
NDA actually covers that datasheet. So knowing the exact details really
helps.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
prev parent reply other threads:[~2022-08-09 13:23 UTC|newest]
Thread overview: 23+ 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 ` medadyoung
2022-06-10 8:43 ` [PATCH v12 1/3] dt-bindings: edac: nuvoton: add NPCM memory controller medadyoung
2022-06-10 8:43 ` medadyoung
2022-06-20 16:40 ` Borislav Petkov
2022-06-20 16:40 ` Borislav Petkov
2022-08-08 6:40 ` Medad Young
2022-08-08 6:40 ` Medad Young
2022-08-09 0:58 ` Kun-Fa Lin
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-10 8:43 ` medadyoung
2022-06-20 17:29 ` Borislav Petkov
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-10 8:43 ` medadyoung
2022-06-20 19:20 ` Borislav Petkov
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 6:42 ` Paul Menzel
2022-08-09 7:50 ` Borislav Petkov
2022-08-09 7:50 ` Borislav Petkov
2022-08-09 13:16 ` Michael Richardson [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=28431.1660051012@localhost \
--to=mcr@sandelman.ca \
--cc=openbmc@lists.ozlabs.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.