Messages in this thread | | | Subject | Re: [PATCH 33/42] drm/ttm/ttm_range_manager: Demote non-conformant kernel-doc header | From | Christian König <> | Date | Mon, 16 Nov 2020 21:34:36 +0100 |
| |
Am 16.11.20 um 18:41 schrieb Lee Jones: > Fixes the following W=1 kernel build warning(s): > > drivers/gpu/drm/ttm/ttm_range_manager.c:46: warning: cannot understand function prototype: 'struct ttm_range_manager ' > > Cc: Christian Koenig <christian.koenig@amd.com> > Cc: Huang Rui <ray.huang@amd.com> > Cc: David Airlie <airlied@linux.ie> > Cc: Daniel Vetter <daniel@ffwll.ch> > Cc: dri-devel@lists.freedesktop.org > Signed-off-by: Lee Jones <lee.jones@linaro.org>
Reviewed-by: Christian König <christian.koenig@amd.com>
> --- > drivers/gpu/drm/ttm/ttm_range_manager.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/ttm/ttm_range_manager.c b/drivers/gpu/drm/ttm/ttm_range_manager.c > index ea77919569a2e..e0952444cea93 100644 > --- a/drivers/gpu/drm/ttm/ttm_range_manager.c > +++ b/drivers/gpu/drm/ttm/ttm_range_manager.c > @@ -37,7 +37,7 @@ > #include <linux/spinlock.h> > #include <linux/module.h> > > -/** > +/* > * Currently we use a spinlock for the lock, but a mutex *may* be > * more appropriate to reduce scheduling latency if the range manager > * ends up with very fragmented allocation patterns.
| |