[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<MWHPR1801MB1918BEA18A733CA492D1CDF5D37E2@MWHPR1801MB1918.namprd18.prod.outlook.com>
Date: Mon, 29 Jan 2024 05:24:35 +0000
From: Ratheesh Kannoth <rkannoth@...vell.com>
To: Simon Horman <horms@...nel.org>, Brett Creeley <bcreeley@....com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Sunil Kovvuri
Goutham <sgoutham@...vell.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org"
<kuba@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>,
Subbaraya Sundeep
Bhatta <sbhatta@...vell.com>,
Geethasowjanya Akula <gakula@...vell.com>,
Hariprasad Kelam <hkelam@...vell.com>
Subject: RE: [EXT] Re: [PATCH net] octeontx2-af: Initialize bitmap arrays.
> From: Simon Horman <horms@...nel.org>
> Subject: Re: [EXT] Re: [PATCH net] octeontx2-af: Initialize bitmap arrays.
> > mcam->bmap = kmalloc_array(BITS_TO_LONGS(mcam-
> >bmap_entries),
> > + sizeof(long), GFP_KERNEL | __GFP_ZERO);
> >
> > This is exactly what bitmap_zalloc()->bitmap_alloc() are doing.
>
> Yes, I agree and I should have suggested using
> bitmap_zalloc() and bitmap_free().
>
ACK.
Powered by blists - more mailing lists