intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] drm: strict type checking for drm_device based logging helpers
Date: Tue, 04 Mar 2025 17:07:07 +0200	[thread overview]
Message-ID: <87eczczvfo.fsf@intel.com> (raw)
In-Reply-To: <cover.1737644530.git.jani.nikula@intel.com>

On Thu, 23 Jan 2025, Jani Nikula <jani.nikula@intel.com> wrote:
> Fix all cases that pass something other than struct drm_device to the
> drm_device based logging helpers, and add strict type checking.
>
> Gustavo Sousa (1):
>   drm/print: Include drm_device.h

This was pushed earlier, independently.

>
> Jani Nikula (4):
>   drm/mipi-dsi: stop passing non struct drm_device to drm_err() and
>     friends
>   drm/rockchip: stop passing non struct drm_device to drm_err() and
>     friends
>   drm/sched: stop passing non struct drm_device to drm_err() and friends
>   drm/print: require struct drm_device for drm_err() and friends

Series pushed to drm-misc-next, thanks for the reviews.

BR,
Jani.

>
>  drivers/gpu/drm/drm_mipi_dsi.c                | 12 +++---
>  drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c   | 16 +++----
>  .../gpu/drm/rockchip/dw_hdmi_qp-rockchip.c    | 16 +++----
>  drivers/gpu/drm/scheduler/sched_entity.c      |  2 +-
>  drivers/gpu/drm/scheduler/sched_main.c        | 20 +++++----
>  include/drm/drm_print.h                       | 42 +++++++++++--------
>  6 files changed, 58 insertions(+), 50 deletions(-)

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2025-03-04 15:07 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 15:09 [PATCH 0/5] drm: strict type checking for drm_device based logging helpers Jani Nikula
2025-01-23 15:09 ` [PATCH 1/5] drm/mipi-dsi: stop passing non struct drm_device to drm_err() and friends Jani Nikula
2025-02-25 16:52   ` Luca Ceresoli
2025-01-23 15:09 ` [PATCH 2/5] drm/rockchip: " Jani Nikula
2025-01-24  9:53   ` Andy Yan
2025-01-24 11:43     ` Jani Nikula
2025-01-25  3:53       ` Andy Yan
2025-02-25 19:34         ` Jani Nikula
2025-02-26  8:33         ` [PATCH " Thomas Zimmermann
2025-02-26 10:36           ` Andy Yan
2025-02-26 11:33             ` Jani Nikula
2025-02-24 14:47   ` Louis Chauvet
2025-01-23 15:09 ` [PATCH 3/5] drm/sched: " Jani Nikula
2025-01-23 19:54   ` Simona Vetter
2025-01-24 11:46     ` Jani Nikula
2025-01-27 10:11       ` Philipp Stanner
2025-02-24 15:29       ` Tvrtko Ursulin
2025-02-24 14:48   ` Louis Chauvet
2025-01-23 15:09 ` [PATCH 4/5] drm/print: Include drm_device.h Jani Nikula
2025-01-23 15:14   ` Jani Nikula
2025-01-23 16:14     ` Gustavo Sousa
2025-01-24 11:50       ` Jani Nikula
2025-01-24 12:21         ` Gustavo Sousa
2025-01-24 12:55           ` Simona Vetter
2025-01-23 15:09 ` [PATCH 5/5] drm/print: require struct drm_device for drm_err() and friends Jani Nikula
2025-02-24 14:48   ` Louis Chauvet
2025-02-25 16:52   ` Luca Ceresoli
2025-05-15 20:18   ` Bill Wendling
2025-05-15 23:52     ` Bill Wendling
2025-05-16  9:48     ` Jani Nikula
2025-05-16 20:41       ` Bill Wendling
2025-01-23 16:05 ` ✗ Fi.CI.SPARSE: warning for drm: strict type checking for drm_device based logging helpers Patchwork
2025-01-23 16:13 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-24  8:26 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-04 15:07 ` Jani Nikula [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=87eczczvfo.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).