From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [Intel-gfx] [PATCH 1/8] drm/print: introduce new struct drm_device based logging macros
Date: Tue, 10 Dec 2019 14:34:33 +0200 [thread overview]
Message-ID: <87o8wge4va.fsf@intel.com> (raw)
In-Reply-To: <20191210123050.8799-1-jani.nikula@intel.com>
On Tue, 10 Dec 2019, Jani Nikula <jani.nikula@intel.com> wrote:
> Add new struct drm_device based logging macros modeled after the core
> kernel device based logging macros. These would be preferred over the
> drm printk and struct device based macros in drm code, where possible.
As to cover letter, patches 2-8 using the logging macros introduced here
are just the beginning. It's not trivial to write a cocci script to dig
up struct drm_device * where there is none, so much of it may need to be
done manually. But we could start here.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-10 12:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 12:30 [Intel-gfx] [PATCH 1/8] drm/print: introduce new struct drm_device based logging macros Jani Nikula
2019-12-10 12:30 ` [Intel-gfx] [PATCH 2/8] drm/client: convert to drm device based logging Jani Nikula
2019-12-17 18:51 ` Sam Ravnborg
2019-12-10 12:30 ` [Intel-gfx] [PATCH 3/8] drm/fb-helper: " Jani Nikula
2019-12-17 18:56 ` Sam Ravnborg
2019-12-10 12:30 ` [Intel-gfx] [PATCH 4/8] drm/gem-fb-helper: " Jani Nikula
2019-12-17 18:57 ` Sam Ravnborg
2019-12-19 14:23 ` Jani Nikula
2019-12-10 12:30 ` [Intel-gfx] [PATCH 5/8] drm/mipi-dbi: " Jani Nikula
2019-12-17 19:00 ` Sam Ravnborg
2019-12-17 19:10 ` Sam Ravnborg
2019-12-10 12:30 ` [Intel-gfx] [PATCH 6/8] drm/atomic: " Jani Nikula
2019-12-12 8:07 ` [Intel-gfx] [6/8] " james qian wang (Arm Technology China)
2019-12-12 8:33 ` Jani Nikula
2019-12-17 19:07 ` [Intel-gfx] [PATCH 6/8] " Sam Ravnborg
2019-12-10 12:30 ` [Intel-gfx] [PATCH 7/8] drm/i915/uc: " Jani Nikula
2019-12-10 12:30 ` [Intel-gfx] [PATCH 8/8] drm/i915/wopcm: " Jani Nikula
2019-12-10 12:34 ` Jani Nikula [this message]
2019-12-10 22:07 ` [Intel-gfx] [PATCH 1/8] drm/print: introduce new struct drm_device based logging macros Daniel Vetter
2019-12-10 19:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] " Patchwork
2019-12-10 19:52 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2019-12-12 21:53 ` [Intel-gfx] [PATCH 1/8] " Sam Ravnborg
2019-12-13 14:41 ` Jani Nikula
2019-12-13 13:48 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] drm/print: introduce new struct drm_device based logging macros (rev2) Patchwork
2019-12-13 15:01 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2019-12-13 19:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] drm/print: introduce new struct drm_device based logging macros (rev3) Patchwork
2019-12-13 20:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-14 16:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2019-12-17 14:45 ` [Intel-gfx] [PATCH 1/8] drm/print: introduce new struct drm_device based logging macros Jani Nikula
2019-12-17 16:11 ` Sam Ravnborg
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=87o8wge4va.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox