[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PH0PR18MB4734672BE30C49F09E2C7D65C7D4A@PH0PR18MB4734.namprd18.prod.outlook.com>
Date: Thu, 19 Oct 2023 18:46:09 +0000
From: Shinas Rasheed <srasheed@...vell.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "horms@...nel.org" <horms@...nel.org>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com"
<edumazet@...gle.com>,
"egallen@...hat.com" <egallen@...hat.com>,
Haseeb Gani
<hgani@...vell.com>,
"mschmidt@...hat.com" <mschmidt@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Sathesh B Edara
<sedara@...vell.com>,
Veerasenareddy Burru <vburru@...vell.com>,
Vimlesh
Kumar <vimleshk@...vell.com>
Subject: Re: [EXT] Re: [net-next PATCH v3] octeon_ep: pack hardware structure
Hi Jakub,
Since these structures represent how hardware expects data, there can be a lack of alignment. I'm afraid static asserting all the hardware data structures might force some compilers to fail?
Powered by blists - more mailing lists