From: Markus Armbruster <armbru@redhat.com>
To: Peter Delevoryas <pdel@fb.com>
Cc: "samuel.thibault@ens-lyon.org" <samuel.thibault@ens-lyon.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"eblake@redhat.com" <eblake@redhat.com>,
Cameron Esfahani via <qemu-devel@nongnu.org>
Subject: Re: [PATCH 3/4] slirp: Add mfr-id to -netdev options
Date: Tue, 21 Jun 2022 11:01:28 +0200 [thread overview]
Message-ID: <87pmj2v193.fsf@pond.sub.org> (raw)
In-Reply-To: <199AAE52-91F7-44A1-8862-ECCE1A347EFC@fb.com> (Peter Delevoryas's message of "Mon, 20 Jun 2022 21:27:38 +0000")
Peter Delevoryas <pdel@fb.com> writes:
> On Jun 20, 2022, at 12:16 AM, Markus Armbruster <armbru@redhat.com<mailto:armbru@redhat.com>> wrote:
[...]
>> Documentation is rather terse. It basically provides a bunch of
>> keywords you can throw at the search engine of your choice. Can we cut
>> out that middle man and point straight to a suitable resource?
>
> Erg, yeah, sorry about that, you’re right, it would probably be more useful
> to point to the NC-SI specification directly:
>
> https://www.dmtf.org/sites/default/files/standards/documents/DSP0222_1.0.0.pdf
>
> Note: there have been some newer revisions to the specification lately, and the
> full list of spec versions is here:
>
> https://www.dmtf.org/dsp/DSP0222
>
> Get Version ID and the OEM Vendor extension are both specified in 1.0.0, so I
> think it should be ok to link to 1.0.0.
>
> I’m not totally sure if I should directly link to the actual URL, but I’ll
> definitely say: “This is defined in DMTF NC-SI 1.0.0” or something like that.
Works for me with the full name of the spec: "DMTF Network Controller
Sideband Interface (NC-SI) Specification, version 1.0.0". You can omit
the version if there are no earlier ones.
> Unless URL’s in the code would be preferred. Theoretically, the DMTF
> spec URL should be pretty long-lasting.
Feel free to add URL, too.
next prev parent reply other threads:[~2022-06-21 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 1:05 [PATCH 0/4] slirp: Update submodule to include NC-SI features Peter Delevoryas
2022-06-16 1:05 ` [PATCH 1/4] slirp: Update submodule to include NC-SI updates Peter Delevoryas
2022-06-16 1:05 ` [PATCH 2/4] slirp: Update SlirpConfig version to 5 Peter Delevoryas
2022-06-18 10:03 ` Samuel Thibault
2022-06-20 21:33 ` Peter Delevoryas
2022-06-16 1:05 ` [PATCH 3/4] slirp: Add mfr-id to -netdev options Peter Delevoryas
2022-06-18 10:05 ` Samuel Thibault
2022-06-20 22:58 ` Peter Delevoryas
2022-06-20 7:16 ` Markus Armbruster
2022-06-20 21:27 ` Peter Delevoryas
2022-06-21 9:01 ` Markus Armbruster [this message]
2022-06-16 1:05 ` [PATCH 4/4] slirp: Add oob-eth-addr " Peter Delevoryas
2022-06-18 10:05 ` Samuel Thibault
2022-06-20 23:01 ` Peter Delevoryas
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=87pmj2v193.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=pdel@fb.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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.