The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: robert.foss@collabora.com
Cc: David Airlie <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] include/drm: Reword debug categories comment.
Date: Thu, 14 Apr 2016 16:52:48 +0200	[thread overview]
Message-ID: <20160414145248.GM2510@phenom.ffwll.local> (raw)
In-Reply-To: <1460644456-9752-1-git-send-email-robert.foss@collabora.com>

On Thu, Apr 14, 2016 at 10:34:16AM -0400, robert.foss@collabora.com wrote:
> From: Robert Foss <robert.foss@collabora.com>
> 
> The debug category comment mentions 4 categories, but
> more than 4 categories are listed. Let's change the
> wording to something a bit more generic.
> 
> Signed-off-by: Robert Foss <robert.foss@collabora.com>

Applied to drm-misc, thanks.
-Daniel

> ---
>  include/drm/drmP.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/drm/drmP.h b/include/drm/drmP.h
> index 3c8422c..5de4cff0 100644
> --- a/include/drm/drmP.h
> +++ b/include/drm/drmP.h
> @@ -90,7 +90,7 @@ struct reservation_object;
>  struct dma_buf_attachment;
>  
>  /*
> - * 4 debug categories are defined:
> + * The following categories are defined:
>   *
>   * CORE: Used in the generic drm code: drm_ioctl.c, drm_mm.c, drm_memory.c, ...
>   *	 This is the category used by the DRM_DEBUG() macro.
> -- 
> 2.5.0
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

      reply	other threads:[~2016-04-14 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14 14:34 [PATCH] include/drm: Reword debug categories comment robert.foss
2016-04-14 14:52 ` Daniel Vetter [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=20160414145248.GM2510@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.foss@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox