All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/debugfs_crc: Degrade ERROR when overflowing to INFO
Date: Thu, 27 Dec 2018 10:05:39 +0200	[thread overview]
Message-ID: <87ftujwg18.fsf@intel.com> (raw)
In-Reply-To: <20181220151726.30641-1-maarten.lankhorst@linux.intel.com>

On Thu, 20 Dec 2018, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:

Insert commit message explaining why here. ;)

BR,
Jani.

> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
>  drivers/gpu/drm/drm_debugfs_crc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_debugfs_crc.c b/drivers/gpu/drm/drm_debugfs_crc.c
> index 00e743153e94..80f473ce5c67 100644
> --- a/drivers/gpu/drm/drm_debugfs_crc.c
> +++ b/drivers/gpu/drm/drm_debugfs_crc.c
> @@ -408,7 +408,7 @@ int drm_crtc_add_crc_entry(struct drm_crtc *crtc, bool has_frame,
>  		spin_unlock(&crc->lock);
>  
>  		if (!was_overflow)
> -			DRM_ERROR("Overflow of CRC buffer, userspace reads too slow.\n");
> +			DRM_INFO("Overflow of CRC buffer, userspace reads too slow.\n");
>  
>  		return -ENOBUFS;
>  	}

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2018-12-27  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 15:17 [PATCH] drm/debugfs_crc: Degrade ERROR when overflowing to INFO Maarten Lankhorst
2018-12-20 16:15 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-12-20 16:36 ` ✓ Fi.CI.BAT: success " Patchwork
2018-12-21 15:25 ` ✓ Fi.CI.IGT: " Patchwork
2018-12-27  8:05 ` Jani Nikula [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ftujwg18.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.