Am 16.07.2014 11:40, schrieb Michel D?nzer:
> From: Michel D?nzer <michel.daenzer at amd.com>
>
> These clutter up dmesg during piglit runs. Userspace generally deals
> gracefully with this failure.
>
> Signed-off-by: Michel D?nzer <michel.daenzer at amd.com>
Reviewed-by: Christian K?nig <christian.koenig at amd.com>
Already wanted to suggest the same thing,
Christian.
> ---
> drivers/gpu/drm/radeon/radeon_gem.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/radeon/radeon_gem.c
> b/drivers/gpu/drm/radeon/radeon_gem.c
> index 07292aa..8584e43 100644
> --- a/drivers/gpu/drm/radeon/radeon_gem.c
> +++ b/drivers/gpu/drm/radeon/radeon_gem.c
> @@ -58,8 +58,8 @@ int radeon_gem_object_create(struct radeon_device *rdev,
> int size,
> /* maximun bo size is the minimun btw visible vram and gtt size */
> max_size = min(rdev->mc.visible_vram_size, rdev->mc.gtt_size);
> if (size > max_size) {
> - printk(KERN_WARNING "%s:%d alloc size %dMb bigger than %ldMb
> limit\n",
> - __func__, __LINE__, size >> 20, max_size >> 20);
> + DRM_DEBUG("Allocation size %dMb bigger than %ldMb limit\n",
> + size >> 20, max_size >> 20);
> return -ENOMEM;
> }
>
