[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <E607265CB020454880711A6F96C05A03926AAEDC@hasmsx107.ger.corp.intel.com>
Date: Wed, 27 Jul 2016 07:30:36 +0000
From: "Levy, Amir (Jer)" <amir.jer.levy@...el.com>
To: 'Lukas Wunner' <lukas@...ner.de>
CC: "andreas.noever@...il.com" <andreas.noever@...il.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
thunderbolt-linux <thunderbolt-linux@...el.com>,
"Westerberg, Mika" <mika.westerberg@...el.com>,
"Winkler, Tomas" <tomas.winkler@...el.com>
Subject: RE: [PATCH v4 5/7] thunderbolt: Networking state machine
On Mon, Jul 25 2016, 01:36 AM, Lukas Wunner wrote:
> On Mon, Jul 18, 2016 at 01:00:38PM +0300, Amir Levy wrote:
> > + const unique_id_be proto_uuid =
> APPLE_THUNDERBOLT_IP_PROTOCOL_UUID;
> > +
> > + if (memcmp(proto_uuid, hdr->apple_tbt_ip_proto_uuid,
> > + sizeof(proto_uuid)) != 0) {
>
> You may want to use the uuid_be data type provided by <linux/uuid.h>
> instead of rolling your own, as well as the helper uuid_be_cmp() defined
> ibidem.
>
All the messages in Thunderbolt consist BE DWORDs.
I didn't find uuid definition in the kernel that accurately describes the uuid structure in the messages, which is 4 BE DWORDs.
But on the other hand, all the driver does is copy/compare of uuids, and it can treat uuids as byte array (i.e. uuid_be).
I'll change it in the next patches.
Powered by blists - more mailing lists