On Wed, 10 Mar 2021 17:59:51 -0600, Gustavo A. R. Silva wrote:
> Dynamic memory allocation isn't actually needed and it can be
> replaced by statically allocating memory for struct object
> io_unit_pg3 with 36 hardcoded entries for its GPIOVal array.
>
> Also, this helps the with ongoing efforts
Hi Martin,
On 3/16/21 22:32, Martin K. Petersen wrote:
>
> Gustavo,
>
>> Dynamic memory allocation isn't actually needed and it can be replaced
>> by statically allocating memory for struct object io_unit_pg3 with 36
>> hardcoded entries for its GPIOVal array.
>
> Applied to 5.13/scsi-staging,
Gustavo,
> Dynamic memory allocation isn't actually needed and it can be replaced
> by statically allocating memory for struct object io_unit_pg3 with 36
> hardcoded entries for its GPIOVal array.
Applied to 5.13/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
Dynamic memory allocation isn't actually needed and it can be
replaced by statically allocating memory for struct object
io_unit_pg3 with 36 hardcoded entries for its GPIOVal array.
Also, this helps the with ongoing efforts to enable -Warray-bounds
by fixing the following warning:
4 matches
Mail list logo