From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: run kernel-doc on headers as part of HDRTEST
Date: Tue, 4 Apr 2023 16:54:55 +0200 [thread overview]
Message-ID: <e02c3cbf-8df2-bb90-2ba7-7c2e69eaea74@linux.intel.com> (raw)
In-Reply-To: <20230404090528.173075-1-jani.nikula@intel.com>
On 4/4/2023 11:05 AM, Jani Nikula wrote:
> Enabling kernel-doc warnings in commit aaee4bbe8a1a ("drm/i915: enable
> kernel-doc warnings for CONFIG_DRM_I915_WERROR=y") actually only covers
> the .c files. And it's good for avoiding warnings in W= builds. However,
> we need something more to check for kernel-doc issues in headers. Add it
> as part of the existing HDRTEST.
>
> We have tons of issues, and this unleashes warnings galore on
> CONFIG_DRM_I915_WERROR=y. It doesn't fail the build because (at least
> for now) we don't pass -Werror to kernel-doc.
>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
This will be really helpful.
Acked-by: Nirmoy Das <nirmoy.das@intel.com>
Thanks,
Nirmoy
> ---
> drivers/gpu/drm/i915/Makefile | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/Makefile b/drivers/gpu/drm/i915/Makefile
> index 831e42175165..b739300267c2 100644
> --- a/drivers/gpu/drm/i915/Makefile
> +++ b/drivers/gpu/drm/i915/Makefile
> @@ -387,7 +387,8 @@ always-$(CONFIG_DRM_I915_WERROR) += \
> $(shell cd $(srctree)/$(src) && find * -name '*.h')))
>
> quiet_cmd_hdrtest = HDRTEST $(patsubst %.hdrtest,%.h,$@)
> - cmd_hdrtest = $(CC) $(filter-out $(CFLAGS_GCOV), $(c_flags)) -S -o /dev/null -x c /dev/null -include $<; touch $@
> + cmd_hdrtest = $(CC) $(filter-out $(CFLAGS_GCOV), $(c_flags)) -S -o /dev/null -x c /dev/null -include $<; \
> + $(srctree)/scripts/kernel-doc -none $<; touch $@
>
> $(obj)/%.hdrtest: $(src)/%.h FORCE
> $(call if_changed_dep,hdrtest)
next prev parent reply other threads:[~2023-04-04 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 9:05 [Intel-gfx] [PATCH] drm/i915: run kernel-doc on headers as part of HDRTEST Jani Nikula
2023-04-04 12:22 ` kernel test robot
2023-04-04 12:26 ` Jani Nikula
2023-04-04 16:21 ` Rodrigo Vivi
2023-04-05 10:43 ` Jani Nikula
2023-04-04 13:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-04-04 14:54 ` Das, Nirmoy [this message]
2023-04-04 22:11 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=e02c3cbf-8df2-bb90-2ba7-7c2e69eaea74@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@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