From: Jani Nikula <jani.nikula@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Luca Coelho <luciano.coelho@intel.com>,
Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH drm-misc-next] drm/xe: fix arguments to drm_err_printer()
Date: Tue, 13 Feb 2024 12:04:24 +0200 [thread overview]
Message-ID: <87h6ic8ytz.fsf@intel.com> (raw)
In-Reply-To: <46f95691c86388a510f78187855d69a3d0132b82.camel@linux.intel.com>
On Tue, 13 Feb 2024, Thomas Hellström <thomas.hellstrom@linux.intel.com> wrote:
> On Tue, 2024-02-13 at 10:49 +0200, Jani Nikula wrote:
>> The commit below changed drm_err_printer() arguments, but failed to
>> update all places.
>>
>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> Closes:
>> https://lore.kernel.org/r/20240213120410.75c45763@canb.auug.org.au
>> Fixes: 5e0c04c8c40b ("drm/print: make drm_err_printer() device
>> specific by using drm_err()")
>> Cc: Luca Coelho <luciano.coelho@intel.com>
>> Cc: Maxime Ripard <mripard@kernel.org>
>> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Thanks, pushed to drm-misc-next.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-02-13 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 8:49 [PATCH drm-misc-next] drm/xe: fix arguments to drm_err_printer() Jani Nikula
2024-02-13 8:52 ` ✓ CI.Patch_applied: success for " Patchwork
2024-02-13 8:52 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-13 8:53 ` ✓ CI.KUnit: success " Patchwork
2024-02-13 9:04 ` ✓ CI.Build: " Patchwork
2024-02-13 9:04 ` ✓ CI.Hooks: " Patchwork
2024-02-13 9:05 ` ✓ CI.checksparse: " Patchwork
2024-02-13 9:37 ` [PATCH drm-misc-next] " Thomas Hellström
2024-02-13 10:04 ` Jani Nikula [this message]
2024-02-13 9:42 ` ✓ CI.BAT: success for " Patchwork
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=87h6ic8ytz.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=luciano.coelho@intel.com \
--cc=mripard@kernel.org \
--cc=sfr@canb.auug.org.au \
--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