[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231120111739.31baf90a@kernel.org>
Date: Mon, 20 Nov 2023 11:17:39 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Wen Gu <guwen@...ux.alibaba.com>
Cc: wintera@...ux.ibm.com, wenjia@...ux.ibm.com, hca@...ux.ibm.com,
gor@...ux.ibm.com, agordeev@...ux.ibm.com, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, kgraul@...ux.ibm.com,
jaka@...ux.ibm.com, borntraeger@...ux.ibm.com, svens@...ux.ibm.com,
alibuda@...ux.alibaba.com, tonylu@...ux.alibaba.com,
raspl@...ux.ibm.com, schnelle@...ux.ibm.com,
linux-s390@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 5/7] net/smc: compatible with 128-bits extend
GID of virtual ISM device
On Sun, 19 Nov 2023 21:57:55 +0800 Wen Gu wrote:
> According to virtual ISM support feature defined by SMCv2.1, GIDs of
> virtual ISM device are UUIDs defined by RFC4122, which are 128-bits
> long. So some adaptation work is required. And note that the GIDs of
> existing platform firmware ISM devices still remain 64-bits long.
sparse (C=1 build) complains:
net/smc/smc_clc.c:944:73: warning: incorrect type in argument 1 (different base types)
net/smc/smc_clc.c:944:73: expected unsigned short [usertype] chid
net/smc/smc_clc.c:944:73: got restricted __be16 [usertype] chid
--
pw-bot: cr
Powered by blists - more mailing lists