From: Jonathan Corbet <corbet@lwn.net>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: mchehab@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bug-hunting.rst: Fix an example and a typo in a Sphinx tag
Date: Tue, 31 Oct 2017 02:07:29 -0600 [thread overview]
Message-ID: <20171031020414.3eeebfbc@lwn.net> (raw)
In-Reply-To: <20171020194914.7387-1-christophe.jaillet@wanadoo.fr>
On Fri, 20 Oct 2017 21:49:14 +0200
Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
> - Use the same file name in the explanation and in the example (conex.c vs
> sonixj.c)
> - Add a missing ':' in a :ref: tag which leads to incorrect Shpinx output
> - Add some missing ',' and ';'
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Applied to the docs tree, thanks.
jon
prev parent reply other threads:[~2017-10-31 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 19:49 [PATCH] bug-hunting.rst: Fix an example and a typo in a Sphinx tag Christophe JAILLET
2017-10-31 8:07 ` 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=20171031020414.3eeebfbc@lwn.net \
--to=corbet@lwn.net \
--cc=christophe.jaillet@wanadoo.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@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