Re: [PATCH v3] staging: ccree: fixed sparse pointer signedness warnings.

2018-01-10 Thread Gilad Ben-Yossef
On Wed, Jan 10, 2018 at 3:08 PM, Jeremy Sowden wrote: > On 2018-01-10, at 15:03:01 +0200, Gilad Ben-Yossef wrote: >> On Wed, Jan 10, 2018 at 1:53 PM, Jeremy Sowden wrote: >> > The driver uses a mixture of signed and unsigned integer variables >> > for holding arrays lengths and

Re: [PATCH v3] staging: ccree: fixed sparse pointer signedness warnings.

2018-01-10 Thread Jeremy Sowden
On 2018-01-10, at 15:03:01 +0200, Gilad Ben-Yossef wrote: > On Wed, Jan 10, 2018 at 1:53 PM, Jeremy Sowden wrote: > > The driver uses a mixture of signed and unsigned integer variables > > for holding arrays lengths and indices, which gives rise to sparse > > warnings when the addresses of signed

Re: [PATCH v3] staging: ccree: fixed sparse pointer signedness warnings.

2018-01-10 Thread Gilad Ben-Yossef
Hi Jeremy, On Wed, Jan 10, 2018 at 1:53 PM, Jeremy Sowden wrote: > The driver uses a mixture of signed and unsigned integer variables for > holding arrays lengths and indices, which gives rise to sparse warnings > when the addresses of signed variables are passed to functions

[PATCH v3] staging: ccree: fixed sparse pointer signedness warnings.

2018-01-10 Thread Jeremy Sowden
The driver uses a mixture of signed and unsigned integer variables for holding arrays lengths and indices, which gives rise to sparse warnings when the addresses of signed variables are passed to functions expecting pointers to unsigned integers. This patch fixes those warnings by converting