From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2 3/2] docs: changes: better document Python needs
Date: Sun, 13 Jul 2025 00:25:17 +0200 [thread overview]
Message-ID: <20250713002517.7f52b0e9@foz.lan> (raw)
In-Reply-To: <20250712163155.GA22640@pendragon.ideasonboard.com>
Em Sat, 12 Jul 2025 19:31:55 +0300
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> Hi Mauro,
>
> Thank you for the patch.
>
> On Sat, Jul 12, 2025 at 10:32:38AM +0200, Mauro Carvalho Chehab wrote:
> > Python is listed as an optional dependency, but this is not
> > true, as kernel-doc is called during compilation when DRM is
> > enabled. Better document that.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
>
> Isn't it only when CONFIG_DRM_HEADER_TEST is enabled ? That option
> depends on EXPERT && BROKEN, so I wouldn't expect it to be widely
> enabled. A quick grep shows that CONFIG_DRM_I915_WERROR does the same
> (with a dependency on EXPERT but not BROKEN though).
Well, EXPERT is currently enabled on several distros. The three ones I have
it handy all have it:
Fedora 42:
$ grep CONFIG_EXPERT /boot/config*
/boot/config-6.14.9-300.fc42.x86_64:CONFIG_EXPERT=y
/boot/config-6.15.3-200.fc42.x86_64:CONFIG_EXPERT=y
/boot/config-6.15.4-200.fc42.x86_64:CONFIG_EXPERT=y
Ubuntu 24.10:
$ grep CONFIG_EXPERT /boot/config*
/boot/config-6.11.0-26-generic:CONFIG_EXPERT=y
/boot/config-6.8.0-60-generic:CONFIG_EXPERT=y
Debian 12:
$ grep CONFIG_EXPERT /boot/config*
/boot/config-6.1.0-34-amd64:CONFIG_EXPERT=y
/boot/config-6.1.0-37-amd64:CONFIG_EXPERT=y
/boot/config-6.1.0-37-rt-amd64:CONFIG_EXPERT=y
So, expert on distros seem quite common those days.
Fedora has it enabled for a long time. On Fedora 42:
$ grep CONFIG_DRM_WERROR /boot/config*
/boot/config-6.14.9-300.fc42.x86_64:CONFIG_DRM_WERROR=y
/boot/config-6.15.3-200.fc42.x86_64:CONFIG_DRM_WERROR=y
/boot/config-6.15.4-200.fc42.x86_64:CONFIG_DRM_WERROR=y
I would expect to have it enabled on other distros as well.
> Is there something else in DRM that invokes kernel-doc ?
>
> > ---
> > Documentation/process/changes.rst | 9 ++++++++-
> > 1 file changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/process/changes.rst b/Documentation/process/changes.rst
> > index bccfa19b45df..6a7d7c1ee274 100644
> > --- a/Documentation/process/changes.rst
> > +++ b/Documentation/process/changes.rst
> > @@ -61,7 +61,7 @@ Sphinx\ [#f1]_ 3.4.3 sphinx-build --version
> > GNU tar 1.28 tar --version
> > gtags (optional) 6.6.5 gtags --version
> > mkimage (optional) 2017.01 mkimage --version
> > -Python (optional) 3.9.x python3 --version
> > +Python 3.9.x python3 --version
> > GNU AWK (optional) 5.1.0 gawk --version
> > ====================== =============== ========================================
> >
> > @@ -154,6 +154,13 @@ Perl
> > You will need perl 5 and the following modules: ``Getopt::Long``,
> > ``Getopt::Std``, ``File::Basename``, and ``File::Find`` to build the kernel.
> >
> > +Python
> > +------
> > +
> > +At least Python 2.7 or 3.4 is required if CONFIG_DRM is selected to avoid
> > +breaking compilation. Documentation build and kernel-doc won't produce
> > +valid results if version is below 3.7.
Maybe I can place instead CONFIG_DRM_I915_WERROR.
Thanks,
Mauro
next prev parent reply other threads:[~2025-07-12 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1752307866.git.mchehab+huawei@kernel.org>
2025-07-12 8:32 ` Mauro Carvalho Chehab
2025-07-12 16:31 ` Laurent Pinchart
2025-07-12 22:25 ` Mauro Carvalho Chehab [this message]
2025-07-13 9:27 ` Laurent Pinchart
2025-07-24 14:42 ` Jonathan Corbet
2025-07-24 17:43 ` Mauro Carvalho Chehab
2025-07-28 9:28 ` Jani Nikula
2025-07-28 15:33 ` Mauro Carvalho Chehab
2025-07-29 10:45 ` Jani Nikula
2025-07-29 13:44 ` Mauro Carvalho Chehab
2025-07-29 15:04 ` 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=20250713002517.7f52b0e9@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.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