Re: [PATCH] drm/ttm: cleanup BO size handling v2

2020-12-09 Thread kernel test robot
Hi "Christian, I love your patch! Perhaps something to improve: [auto build test WARNING on drm-tip/drm-tip] [also build test WARNING on next-20201209] [cannot apply to drm-exynos/exynos-drm-next drm-intel/for-linux-next tegra-drm/drm/tegra/for-next linus/master drm/drm-next v5.10-rc7] [If your

Re: [PATCH] drm/ttm: cleanup BO size handling v2

2020-12-09 Thread kernel test robot
Hi "Christian, I love your patch! Perhaps something to improve: [auto build test WARNING on drm-tip/drm-tip] [also build test WARNING on next-20201209] [cannot apply to drm-exynos/exynos-drm-next drm-intel/for-linux-next tegra-drm/drm/tegra/for-next linus/master drm/drm-next v5.10-rc7] [If your

Re: [PATCH] drm/ttm: cleanup BO size handling v2

2020-12-09 Thread Daniel Vetter
On Wed, Dec 9, 2020 at 3:10 PM Christian König wrote: > > Based on an idea from Dave, but cleaned up a bit. > > We had multiple fields for essentially the same thing. > > Now bo->base.size is the original size of the BO in > arbitrary units, usually bytes. > > bo->mem.num_pages is the size in numb

[PATCH] drm/ttm: cleanup BO size handling v2

2020-12-09 Thread Christian König
Based on an idea from Dave, but cleaned up a bit. We had multiple fields for essentially the same thing. Now bo->base.size is the original size of the BO in arbitrary units, usually bytes. bo->mem.num_pages is the size in number of pages in the resource domain of bo->mem.mem_type. v2: use the G