From: Johannes Berg <johannes@sipsolutions.net>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v2 1/2] kernel-doc: don't let V=1 change outcome
Date: Tue, 06 Jun 2023 23:07:38 +0200 [thread overview]
Message-ID: <2017a6dba12cc7cd05aec33e8066cb7038a89a31.camel@sipsolutions.net> (raw)
In-Reply-To: <CAK7LNASe+HWuufyANGJJ0dajzSC4LFy=x2N6erGis0+ZQkAAXA@mail.gmail.com>
On Tue, 2023-06-06 at 20:15 +0900, Masahiro Yamada wrote:
> >
> > ifneq ($(KBUILD_EXTRA_WARN),)
> > - cmd_checkdoc = $(srctree)/scripts/kernel-doc -none $<
> > + cmd_checkdoc = $(srctree)/scripts/kernel-doc -none \
> > + $(if $(KDOC_WALL), -Wall) \
> > + $(if $(KDOC_WRETURN), -Wreturn) \
> > + $(if $(KDOC_WSHORT_DESC), -Wshort-desc) \
> > + $(if $(KDOC_WSHORT_DESC), -Wcontents-before-sections) \
>
>
>
> Sorry, I misunderstood your intention.
> (I just thought existing env variables would be moved to Makefile)
>
>
> I do not want to proliferate env variables any more.
Oh, ok, sure.
> If you need per-flag control, maybe we can do like this?
Well honestly, I myself just want to pass -Wall, but not necessarily W=2
since that adds more stuff from the C compiler.
> cmd_checkdoc = $(srctree)/scripts/kernel-doc -none \
> $(KDOCFLAGS)
>
>
> Then, users can do
>
> $ make KDOCFLAGS=-Wall
> $ make KDOCFLAGS=-Wreturn
I'd rather call it KDOC_FLAGS if you don't mind to align with
KDOC_WERROR which we have already, but sure, can do.
johannes
next prev parent reply other threads:[~2023-06-06 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:57 Johannes Berg
2023-06-06 8:57 ` [PATCH v2 2/2] kbuild: enable kernel-doc -Wall for W=2 Johannes Berg
2023-06-06 11:15 ` [PATCH v2 1/2] kernel-doc: don't let V=1 change outcome Masahiro Yamada
2023-06-06 21:07 ` Johannes Berg [this message]
2023-06-07 23:51 ` Masahiro Yamada
2023-06-09 8:42 ` Johannes Berg
2023-06-09 8:26 ` Jonathan Corbet
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=2017a6dba12cc7cd05aec33e8066cb7038a89a31.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.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
all inboxes | Powered by JetHome®