From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: add DRM_ERROR_RATELIMITED
Date: Fri, 22 Nov 2013 16:34:25 +0100 [thread overview]
Message-ID: <20131122153424.GD1741@ulmo.nvidia.com> (raw)
In-Reply-To: <1385062191-30854-1-git-send-email-robdclark@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 302 bytes --]
On Thu, Nov 21, 2013 at 02:29:51PM -0500, Rob Clark wrote:
> For error traces in situations that can run away, it is nice to have a
> rate-limited version of DRM_ERROR() to avoid massing log flooding.
s/massing/massive/?
Other than that, looks good:
Reviewed-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-11-22 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 19:29 [PATCH] drm: add DRM_ERROR_RATELIMITED Rob Clark
2013-11-22 15:34 ` Thierry Reding [this message]
2013-11-22 16:37 ` Rob Clark
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=20131122153424.GD1741@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robdclark@gmail.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.