Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simona Vetter <simona.vetter@ffwll.ch>
To: Jani Nikula <jani.nikula@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, simona.vetter@ffwll.ch
Subject: Re: [PATCH 0/2] drm: add header tests
Date: Thu, 23 Jan 2025 15:55:24 +0100	[thread overview]
Message-ID: <Z5JYXICinxvDXN2J@phenom.ffwll.local> (raw)
In-Reply-To: <cover.1737556766.git.jani.nikula@intel.com>

On Wed, Jan 22, 2025 at 04:41:32PM +0200, Jani Nikula wrote:
> Add CONFIG_DRM_HEADER_TEST to ensure drm headers are self-contained and
> pass kernel-doc. And for starters, fix one header that this catches.
> 
> Jani Nikula (2):
>   drm/client: include types.h to make drm_client_event.h self-contained
>   drm: ensure drm headers are self-contained and pass kernel-doc

I guess we should give this another shot. On the series:

Acked-by: Simona Vetter <simona.vetter@ffwll.ch>


> 
>  Kbuild                         |  1 +
>  drivers/gpu/drm/Kconfig        | 11 +++++++++++
>  drivers/gpu/drm/Makefile       | 18 ++++++++++++++++++
>  include/Kbuild                 |  1 +
>  include/drm/Makefile           | 18 ++++++++++++++++++
>  include/drm/drm_client_event.h |  2 ++
>  6 files changed, 51 insertions(+)
>  create mode 100644 include/Kbuild
>  create mode 100644 include/drm/Makefile
> 
> -- 
> 2.39.5
> 

-- 
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  parent reply	other threads:[~2025-01-23 14:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 14:41 [PATCH 0/2] drm: add header tests Jani Nikula
2025-01-22 14:41 ` [PATCH 1/2] drm/client: include types.h to make drm_client_event.h self-contained Jani Nikula
2025-01-22 14:41 ` [PATCH 2/2] drm: ensure drm headers are self-contained and pass kernel-doc Jani Nikula
2025-03-02 16:01   ` Masahiro Yamada
2025-03-03 10:02     ` Jani Nikula
2025-03-03 12:59       ` Masahiro Yamada
2025-03-03 13:52         ` Jani Nikula
2025-03-04 18:05           ` Masahiro Yamada
2025-03-05 13:59             ` Maxime Ripard
2025-03-08 17:05               ` Masahiro Yamada
2025-03-13 10:59                 ` Jani Nikula
2025-01-22 15:23 ` ✗ Fi.CI.CHECKPATCH: warning for drm: add header tests Patchwork
2025-01-22 15:23 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-01-22 15:37 ` ✗ i915.CI.BAT: failure " Patchwork
2025-01-23 14:55 ` Simona Vetter [this message]
2025-02-12 10:26   ` [PATCH 0/2] " 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=Z5JYXICinxvDXN2J@phenom.ffwll.local \
    --to=simona.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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