linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Salvatore Bonaccorso <carnil@debian.org>,
	linux-doc@vger.kernel.org,
	Bhaskar Chowdhury <unixbhaskar@gmail.com>,
	LinuxKernel <linux-kernel@vger.kernel.org>,
	jforbes@fedoraproject.org
Subject: Re: Documentation: build failure with sphinx >= 3.0.0: exception: cannot import name 'c_funcptr_sig_re' from 'sphinx.domains.c'
Date: Wed, 12 Aug 2020 07:18:01 -0600	[thread overview]
Message-ID: <20200812071801.71d44fe2@lwn.net> (raw)
In-Reply-To: <579fbb36-515d-5af4-f7dc-c092d29fddd8@darmarit.de>

On Wed, 12 Aug 2020 10:21:40 +0200
Markus Heiser <markus.heiser@darmarit.de> wrote:

> @jon, do you have time to implement a patch?
> .. sorry, I'am in a hurry :o

This is on my list ... but life is busy at the moment.  I would not be
distressed if somebody beat me to it.

jon

      parent reply	other threads:[~2020-08-12 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200408113705.GB1924@ArchLinux>
     [not found] ` <20200408132505.52e595bc@lwn.net>
     [not found]   ` <20200408233450.GA14923@debian>
2020-08-09 13:23     ` Documentation: build failure with sphinx >= 3.0.0: exception: cannot import name 'c_funcptr_sig_re' from 'sphinx.domains.c' (was: Re: Kernel build failed ...SPHINX extension error) Salvatore Bonaccorso
2020-08-12  7:30       ` Documentation: build failure with sphinx >= 3.0.0: exception: cannot import name 'c_funcptr_sig_re' from 'sphinx.domains.c' Salvatore Bonaccorso
2020-08-12  8:21         ` Markus Heiser
2020-08-12 12:44           ` Markus Heiser
2020-08-12 13:18           ` Jonathan Corbet [this message]

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=20200812071801.71d44fe2@lwn.net \
    --to=corbet@lwn.net \
    --cc=carnil@debian.org \
    --cc=jforbes@fedoraproject.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    --cc=unixbhaskar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).