From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: peter@bikeshed.quignogs.org.uk
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 1/1] Changed double colon to single colon at the ends of two paragraphs preceding ".. code-block:: c".
Date: Mon, 9 Mar 2020 09:02:32 +0100 [thread overview]
Message-ID: <20200309080232.GE2376@latitude> (raw)
In-Reply-To: <20200309000421.9397-1-peter@bikeshed.quignogs.org.uk>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
Hello Peter,
On Mon, Mar 09, 2020 at 12:04:21AM +0000, peter@bikeshed.quignogs.org.uk wrote:
> -is a typical example of a cascaded interrupt handler using gpio_irq_chip::
> +is a typical example of a cascaded interrupt handler using gpio_irq_chip:
Mauro has already fixed this in linux-next:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c1c8b1ff0a1985d4992f49a5775bbcf6ee5ccfba
I'm sure there's still plenty of other stuff to fix, though!
Thanks,
Jonathan Neuschäfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-03-09 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 0:04 [PATCH 1/1] Changed double colon to single colon at the ends of two paragraphs preceding ".. code-block:: c" peter
2020-03-09 8:02 ` Jonathan Neuschäfer [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=20200309080232.GE2376@latitude \
--to=j.neuschaefer@gmx.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=peter@bikeshed.quignogs.org.uk \
/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).