From: Jeremy Kerr <jk@codeconstruct.com.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Matt Johnston <matt@codeconstruct.com.au>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
Santosh Puranik <spuranik@nvidia.com>
Subject: Re: [PATCH net-next 1/2] usb: Add base USB MCTP definitions
Date: Thu, 06 Feb 2025 15:36:05 +0800 [thread overview]
Message-ID: <829b7f7688e701fd246fdac717fd3fd7efc81d65.camel@codeconstruct.com.au> (raw)
In-Reply-To: <2025020634-statute-ribbon-90a8@gregkh>
>
Hi Greg,
> > Can do. I have one in the actual driver, but can replicate that
> > here if it's helpful.
>
> Isn't this a usb.org spec and not a vendor-specific one?
Nope, all defined by the DMTF - so not really a vendor, but external to
the USB-IF at least. The only mention of this under USB-IF is the class
code allocation, along with the note:
[0x14] This base class is defined for devices that conform to the
“MCTP over USB” found at the DMTF website as DSP0283. This
specification defines the usable set of SubClass and Protocol
values. Values outside of this defined spec are reserved. These
class codes can only be used in Interface Descriptors.
> As per copyright norms, list the real dates, so that would be:
> Copyright (C) 2024-2025 ...
ack, will do.
Cheers,
Jeremy
next prev parent reply other threads:[~2025-02-06 7:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 6:48 [PATCH net-next 0/2] mctp: Add MCTP-over-USB hardware transport binding Jeremy Kerr
2025-02-06 6:48 ` [PATCH net-next 1/2] usb: Add base USB MCTP definitions Jeremy Kerr
2025-02-06 7:03 ` Greg Kroah-Hartman
2025-02-06 7:11 ` Jeremy Kerr
2025-02-06 7:22 ` Greg Kroah-Hartman
2025-02-06 7:36 ` Jeremy Kerr [this message]
2025-02-06 8:14 ` Greg Kroah-Hartman
2025-02-06 6:48 ` [PATCH net-next 2/2] net: mctp: Add MCTP USB transport driver Jeremy Kerr
2025-02-06 7:07 ` Greg Kroah-Hartman
2025-02-07 8:49 ` Jeremy Kerr
2025-02-07 9:10 ` Greg Kroah-Hartman
2025-02-07 9:45 ` Jeremy Kerr
2025-02-07 12:18 ` Greg Kroah-Hartman
2025-02-06 11:12 ` Oliver Neukum
2025-02-07 7:45 ` Jeremy Kerr
2025-02-07 15:26 ` Simon Horman
2025-02-10 1:57 ` Jeremy Kerr
2025-02-20 18:13 ` Jeff Johnson
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=829b7f7688e701fd246fdac717fd3fd7efc81d65.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=spuranik@nvidia.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