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, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2 1/2] kernel-doc: don't let V=1 change outcome
Date: Fri, 09 Jun 2023 10:42:42 +0200 [thread overview]
Message-ID: <4d93871f8b87c9d1e384f52619fe14433c5bc6a0.camel@sipsolutions.net> (raw)
In-Reply-To: <CAK7LNAROju1ob-5VKEsu_UOfCNoMRE-QU27JE3Ndh-M7pBraSw@mail.gmail.com>
On Thu, 2023-06-08 at 08:51 +0900, Masahiro Yamada wrote:
> >
> > > 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.
>
>
> I just tried to be consistent with
> CPPFLAGS, CFLAGS, AFLAGS, CHECKFLAGS etc.
> (CHECKFLAGS is for sparse) because
> you apparently mimick compiler flags in kernel-doc.
OK, sure, works for me. I made it mimic compiler flags because it was
already doing it for -Werror :)
> BTW, kernel-doc is invoked from Documentation/Makefile too.
>
> Do we need to pass the same flags to both of them?
It doesn't look like we _can_ in that case, at least not from the build
system, it'd have to be in kerneldoc.py or something. I also didn't
think it was that important, so I left it.
johannes
next prev parent reply other threads:[~2023-06-09 8:43 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
2023-06-07 23:51 ` Masahiro Yamada
2023-06-09 8:42 ` Johannes Berg [this message]
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=4d93871f8b87c9d1e384f52619fe14433c5bc6a0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=corbet@lwn.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®