From: Jani Nikula <jani.nikula@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: dri-devel@lists.freedesktop.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: Re: [PATCH 09/10] drm/xe: switch from drm_debug_printer() to device specific drm_dbg_printer()
Date: Fri, 09 Feb 2024 14:07:22 +0200 [thread overview]
Message-ID: <87r0hlalj9.fsf@intel.com> (raw)
In-Reply-To: <yivsrvud5khq4vjl5g4aigjwru4zyxfzp7bgzzxcifchpv7kll@4bdjrna2levy>
On Thu, 01 Feb 2024, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> Do you plan to also merge the last patch where you remove
> drm_debug_printer()? Any conflict to be solved in the merge commit?
>
> This is just a question to know what's the plan, not preferring
> something else.
I looked into it, didn't see any conflicts, and merged away. Hopefully
none pop up until the branches merge again.
> Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
Thanks,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-09 12:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 13:07 [PATCH 00/10] drm: drm debug and error logging improvements Jani Nikula
2024-01-16 13:07 ` [PATCH 01/10] drm/print: make drm_err_printer() device specific by using drm_err() Jani Nikula
2024-01-30 10:08 ` Luca Coelho
2024-01-16 13:07 ` [PATCH 02/10] drm/print: move enum drm_debug_category etc. earlier in drm_print.h Jani Nikula
2024-01-30 10:11 ` Luca Coelho
2024-01-16 13:07 ` [PATCH 03/10] drm/print: add drm_dbg_printer() for drm device specific printer Jani Nikula
2024-01-30 10:19 ` Luca Coelho
2024-01-16 13:07 ` [PATCH 04/10] drm/dp_mst: switch from drm_debug_printer() to device specific drm_dbg_printer() Jani Nikula
2024-01-30 10:20 ` Luca Coelho
2024-01-16 13:07 ` [PATCH 05/10] drm/mode: " Jani Nikula
2024-01-30 10:23 ` Luca Coelho
2024-01-16 13:07 ` [PATCH 06/10] drm/dp: switch drm_dp_vsc_sdp_log() to struct drm_printer Jani Nikula
2024-01-30 10:26 ` Luca Coelho
2024-01-16 13:07 ` [PATCH 07/10] drm/i915: switch from drm_debug_printer() to device specific drm_dbg_printer() Jani Nikula
2024-01-30 10:27 ` Luca Coelho
2024-01-16 13:07 ` [PATCH 08/10] drm/i915: use drm_printf() with the drm_err_printer intead of pr_err() Jani Nikula
2024-01-30 10:28 ` Luca Coelho
2024-01-16 13:07 ` [PATCH 09/10] drm/xe: switch from drm_debug_printer() to device specific drm_dbg_printer() Jani Nikula
2024-01-30 10:32 ` Luca Coelho
2024-02-01 12:52 ` Jani Nikula
2024-02-01 16:16 ` Lucas De Marchi
2024-02-09 12:07 ` Jani Nikula [this message]
2024-01-16 13:07 ` [PATCH 10/10] drm: remove drm_debug_printer in favor of drm_dbg_printer Jani Nikula
2024-01-30 10:35 ` Luca Coelho
2024-01-16 14:21 ` ✗ Fi.CI.CHECKPATCH: warning for drm: drm debug and error logging improvements (rev2) Patchwork
2024-01-16 14:21 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-01-16 14:33 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-16 15:57 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-02-01 12:51 ` [PATCH 00/10] drm: drm debug and error logging improvements Jani Nikula
2024-02-01 14:43 ` Maxime Ripard
2024-02-09 11:40 ` Jani Nikula
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=87r0hlalj9.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=ogabbay@kernel.org \
--cc=thomas.hellstrom@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).