[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230405122854.GU33314@black.fi.intel.com>
Date: Wed, 5 Apr 2023 15:28:54 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Michael Jamet <michael.jamet@...el.com>,
Yehezkel Bernat <YehezkelShB@...il.com>, netdev@...r.kernel.org
Subject: Re: [PATCH 1/2] net: thunderbolt: Fix sparse warnings
On Wed, Apr 05, 2023 at 01:42:08PM +0300, Andy Shevchenko wrote:
> > How they are different? The complain is pretty much the same for all
> > these AFAICT:
> >
> > expected restricted xxx [usertype] yyy
> > got restricted zzz [usertype]
>
> While the main part is about header data type and endianess conversion between
> protocol and CPU (with cpu_*() and *_cpu() macros) this one is completely network
> related stuff as it's using hton*() and ntoh*() conversion macros. Yes, underneeth
> it may be the same, but semantically these two parts are not of the same thing.
Okay, fair enough :) I'll make this split in v2.
Powered by blists - more mailing lists