All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org,
	Brendan Higgins <brendanhiggins@google.com>,
	linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
	linux-doc@vger.kernel.org, Harinder Singh <sharinder@google.com>,
	Tim Bird <tim.bird@sony.com>
Subject: Re: [PATCH] Documentation: kunit: eliminate code-block warnings
Date: Tue, 28 Jun 2022 08:17:49 +0100	[thread overview]
Message-ID: <20220628081744.7e6955e6@sal.lan> (raw)
In-Reply-To: <4c403239-3c71-4ab9-2168-f7e9d77008b2@infradead.org>

Em Sat, 25 Jun 2022 08:12:00 -0700
Randy Dunlap <rdunlap@infradead.org> escreveu:

> > So which version of Sphinx are you using?  The language argument became
> > optional in 2.0, so you'd need to be running something pretty ancient to
> > see this.
> > 
> > Ah, I see 1.8.5 in your later message...how wedded are you to that
> > version?  
> 
> It's what ships with OpenSuse Leap 15.3, which I have been using for quite
> a long time.
> 
> I see that there is now OpenSuse Leap 15.4, so I could upgrade to that,
> but I don't know what version on Sphinx it uses.

It seems that there are two versions on it, packaged with different
names:

2.3.1:
	https://download.opensuse.org/distribution/leap/15.4/repo/oss/noarch/python3-Sphinx-2.3.1-150400.1.7.noarch.rpm
4.2.0:
	https://download.opensuse.org/distribution/leap/15.4/repo/oss/noarch/python3-Sphinx_4_2_0-4.2.0-150400.11.6.noarch.rpm

It should be noticed that, while we don't decide to remove support for
Sphinx < 3, kernel-doc has two different outputs, depending on Sphinx C
domain support. The legacy support is enabled with version < 3 [1].

As we're currently discussing dropping support for Sphinx version < 3,
I would recommend you to use the 4.2 package.

Regards,
Mauro

[1] Version 3.0 is a bad choice, as the C domain is partially broken.

  reply	other threads:[~2022-06-28  7:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  2:47 [PATCH] Documentation: kunit: eliminate code-block warnings Randy Dunlap
2022-04-01  6:26 ` David Gow
2022-04-02  6:24   ` Randy Dunlap
2022-06-19 23:56 ` Randy Dunlap
2022-06-24 19:27 ` Jonathan Corbet
2022-06-25 15:12   ` Randy Dunlap
2022-06-28  7:17     ` Mauro Carvalho Chehab [this message]
2022-06-28 14:20       ` Randy Dunlap

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=20220628081744.7e6955e6@sal.lan \
    --to=mchehab@kernel.org \
    --cc=brendanhiggins@google.com \
    --cc=corbet@lwn.net \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sharinder@google.com \
    --cc=tim.bird@sony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.