[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <829b7f7688e701fd246fdac717fd3fd7efc81d65.camel@codeconstruct.com.au>
Date: Thu, 06 Feb 2025 15:36:05 +0800
From: Jeremy Kerr <jk@...econstruct.com.au>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Matt Johnston <matt@...econstruct.com.au>, Andrew Lunn
<andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo
Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
linux-usb@...r.kernel.org, Santosh Puranik <spuranik@...dia.com>
Subject: Re: [PATCH net-next 1/2] usb: Add base USB MCTP definitions
>
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
Powered by blists - more mailing lists