From: Haneen Mohammed <hamohammed.sa@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>,
outreachy-kernel <outreachy-kernel@googlegroups.com>,
gregkh@linuxfoundation.org
Subject: [PATCH v3 0/2] drm: Move debug macros out of drmP.h
Date: Tue, 17 Oct 2017 02:38:19 -0600 [thread overview]
Message-ID: <cover.1508228315.git.hamohammed.sa@gmail.com> (raw)
This patchset move debug macros from drmP.h to drm_print.h and move
printing related functions used by the debug macros from drm_drv.[hc]
to drm_print.[hc].
In addition, it fixes old comment style.
Changes in v3:
- Move debug macros and print functions into drm_print.[hc] instead of
introducing drm_debug.[hc].
Haneen Mohammed (2):
drm: Move debug macros out of drmP.h
drm/print: Update old comment style
drivers/gpu/drm/drm_drv.c | 47 --------------
drivers/gpu/drm/drm_print.c | 47 ++++++++++++++
include/drm/drmP.h | 150 +-------------------------------------------
include/drm/drm_drv.h | 7 ---
include/drm/drm_print.h | 149 +++++++++++++++++++++++++++++++++++++++++++
5 files changed, 197 insertions(+), 203 deletions(-)
--
2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: Haneen Mohammed <hamohammed.sa@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: gregkh@linuxfoundation.org,
outreachy-kernel <outreachy-kernel@googlegroups.com>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: [PATCH v3 0/2] drm: Move debug macros out of drmP.h
Date: Tue, 17 Oct 2017 02:38:19 -0600 [thread overview]
Message-ID: <cover.1508228315.git.hamohammed.sa@gmail.com> (raw)
This patchset move debug macros from drmP.h to drm_print.h and move
printing related functions used by the debug macros from drm_drv.[hc]
to drm_print.[hc].
In addition, it fixes old comment style.
Changes in v3:
- Move debug macros and print functions into drm_print.[hc] instead of
introducing drm_debug.[hc].
Haneen Mohammed (2):
drm: Move debug macros out of drmP.h
drm/print: Update old comment style
drivers/gpu/drm/drm_drv.c | 47 --------------
drivers/gpu/drm/drm_print.c | 47 ++++++++++++++
include/drm/drmP.h | 150 +-------------------------------------------
include/drm/drm_drv.h | 7 ---
include/drm/drm_print.h | 149 +++++++++++++++++++++++++++++++++++++++++++
5 files changed, 197 insertions(+), 203 deletions(-)
--
2.7.4
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-10-17 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 8:38 Haneen Mohammed [this message]
2017-10-17 8:38 ` [PATCH v3 0/2] drm: Move debug macros out of drmP.h Haneen Mohammed
2017-10-17 8:43 ` [PATCH v3 1/2] " Haneen Mohammed
2017-10-17 8:43 ` Haneen Mohammed
2017-10-17 19:54 ` Sean Paul
2017-10-17 19:54 ` Sean Paul
2017-10-17 20:29 ` Haneen Mohammed
2017-10-17 20:29 ` Haneen Mohammed
2017-10-17 8:45 ` [PATCH v3 2/2] drm/print: Update old comment style Haneen Mohammed
2017-10-17 8:45 ` Haneen Mohammed
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=cover.1508228315.git.hamohammed.sa@gmail.com \
--to=hamohammed.sa@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jani.nikula@linux.intel.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=seanpaul@chromium.org \
/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.