All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: "WARNING: Duplicate C declaration" from recent Sphinx (was Re: [PATCH] docs: sphinx/requirements: Limit jinja2<3.1)
Date: Sun, 22 May 2022 07:07:07 +0200	[thread overview]
Message-ID: <20220522070707.313e6558@coco.lan> (raw)
In-Reply-To: <6476f6e7-0fc9-a55a-cafc-7b2fc31f6d51@gmail.com>

Em Sun, 22 May 2022 09:57:45 +0900
Akira Yokosawa <akiyks@gmail.com> escreveu:

> On Sat, 21 May 2022 11:46:29 +0200,
> Mauro Carvalho Chehab wrote:
> [...]
> > 
> > Sphinx 4.0 and above: it is now possible to add a namespace. This allows
> > fixing things like read() system calls that have different meanings on
> > different subsystems.
> > 
> > On other words, only with Sphinx 4.0 and above, the cross-references
> > for C domain symbols should all be OK.  
> 
> So, I noticed there is a PR at https://github.com/sphinx-doc/sphinx/pull/8313
> which is still open.

Are you sure? I always believed that this (or a variant of it) got 
merged on 4.0.

> 
> This PR is supposed to resolve "WARNING: Duplicate C declaration"
> due to struct and function with the same name, isn't it?
> 
> Are you sure the issue is resolved in Sphinx 4.0 and later?

You need to ping Sphinx C domain maintainer to be sure. This was
the author of the PR by the time I looked into it, but I'm not
tracking Sphinx development, so things might have changed.

Thanks,
Mauro

  reply	other threads:[~2022-05-22  5:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  6:07 [PATCH] docs: sphinx/requirements: Limit jinja2<3.1 Akira Yokosawa
2022-03-29 13:01 ` Bagas Sanjaya
2022-03-29 14:00   ` Jonathan Corbet
2022-03-29 14:08     ` Akira Yokosawa
2022-03-29 14:01   ` Akira Yokosawa
2022-03-29 15:31 ` Jonathan Corbet
2022-03-29 15:36   ` Randy Dunlap
2022-03-29 23:51     ` Akira Yokosawa
2022-03-30  0:07       ` Randy Dunlap
2022-03-30  0:25   ` Mauro Carvalho Chehab
2022-03-30 14:59     ` Akira Yokosawa
2022-03-30 17:07       ` Mauro Carvalho Chehab
2022-03-31 14:32         ` Akira Yokosawa
2022-05-21  7:58           ` "WARNING: Duplicate C declaration" from recent Sphinx (was Re: [PATCH] docs: sphinx/requirements: Limit jinja2<3.1) Akira Yokosawa
2022-05-21  9:46             ` Mauro Carvalho Chehab
2022-05-21  9:59               ` Akira Yokosawa
2022-05-22  0:57               ` Akira Yokosawa
2022-05-22  5:07                 ` Mauro Carvalho Chehab [this message]
2022-05-22  9:28                   ` Akira Yokosawa
2022-03-30  1:29   ` [PATCH] docs: sphinx/requirements: Limit jinja2<3.1 Akira Yokosawa
2022-03-30 19:44     ` 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=20220522070707.313e6558@coco.lan \
    --to=mchehab@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@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 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.