On Tue, Mar 05, 2019 at 11:28:36AM +0200, Joonas Lahtinen wrote:
> I take it that both instances are supposed to call bitmap_zalloc?
>
> If you can send a v2 that compiles, I can merge it after it passes the
> CI.
v2 had been sent yesterday.
--
With Best Regards,
Andy Shevchenko
Quoting Andy Shevchenko (2019-03-05 10:20:31)
> On Tue, Mar 05, 2019 at 11:28:36AM +0200, Joonas Lahtinen wrote:
> > I take it that both instances are supposed to call bitmap_zalloc?
> >
> > If you can send a v2 that compiles, I can merge it after it passes the
> > CI.
>
> v2 had been sent
I take it that both instances are supposed to call bitmap_zalloc?
If you can send a v2 that compiles, I can merge it after it passes the
CI.
Regards, Joonas
Quoting Andy Shevchenko (2019-03-04 11:03:20)
> Switch to bitmap_zalloc() to show clearly what we are allocating.
> Besides that it
Switch to bitmap_zalloc() to show clearly what we are allocating.
Besides that it returns pointer of bitmap type instead of opaque void *.
Signed-off-by: Andy Shevchenko
---
drivers/gpu/drm/selftests/test-drm_mm.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git
Hi Andy,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v5.0 next-20190301]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Andy,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v5.0 next-20190301]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
