From: Takashi Iwai <tiwai@suse.de>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Jonathan Corbet <corbet@lwn.net>,
Jani Nikula <jani.nikula@intel.com>,
linux-doc@vger.kernel.org
Subject: Re: kernel-doc unbuildable with sphinx 1.7
Date: Fri, 02 Mar 2018 15:44:45 +0100 [thread overview]
Message-ID: <s5hvaeefsf6.wl-tiwai@suse.de> (raw)
In-Reply-To: <895ece54-4bde-47d8-7c0c-adfdd21fdf23@suse.cz>
On Fri, 02 Mar 2018 15:40:37 +0100,
Jiri Slaby wrote:
>
> On 03/02/2018, 03:34 PM, Jonathan Corbet wrote:
> > I got a patch from Takashi this very morning for that problem; I guess
> > I'll have to fast-track it Linusward.
>
> Oh, thanks!
>
> P.S.: Takashi, could you push it to our master & stable branches?
Sure, just waited for the feedback from Jon :)
Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-03-02 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 14:10 kernel-doc unbuildable with sphinx 1.7 Jiri Slaby
2018-03-02 14:34 ` Jonathan Corbet
2018-03-02 14:40 ` Jiri Slaby
2018-03-02 14:44 ` Takashi Iwai [this message]
2018-03-02 14:52 ` 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=s5hvaeefsf6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=corbet@lwn.net \
--cc=jani.nikula@intel.com \
--cc=jslaby@suse.cz \
--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 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).