From: Jonathan Corbet <corbet@lwn.net>
To: Tom Saeger <tom.saeger@oracle.com>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Documentation: fix invalid Documentation refs (2)
Date: Thu, 19 Oct 2017 12:59:15 -0600 [thread overview]
Message-ID: <20171019125915.0ad331e1@lwn.net> (raw)
In-Reply-To: <cover.1507838726.git.tom.saeger@oracle.com>
On Thu, 12 Oct 2017 15:23:26 -0500
Tom Saeger <tom.saeger@oracle.com> wrote:
> Batch (2) set of simple document ref fixes.
>
>
> Tom Saeger (8):
> Documentation: fix locking rt-mutex doc refs
> Documentation: fix ref to sphinx/kerneldoc.py
> Documentation: fix ref to workqueue content
> Documentation: fix ref to coccinelle content
> Documentation: fix ref to trace stm content
> Documentation: fix ref to power basic-pm-debugging
> Documentation: fix selftests related file refs
> Documentation: fix ref to gpio.txt
I've applied the set (except 8/8, which Linus W. already grabbed).
Thanks,
jon
prev parent reply other threads:[~2017-10-19 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:23 [PATCH 0/8] Documentation: fix invalid Documentation refs (2) Tom Saeger
2017-10-12 20:23 ` [PATCH 1/8] Documentation: fix locking rt-mutex doc refs Tom Saeger
2017-10-12 20:23 ` [PATCH 2/8] Documentation: fix ref to sphinx/kerneldoc.py Tom Saeger
2017-10-12 20:23 ` [PATCH 3/8] Documentation: fix ref to workqueue content Tom Saeger
2017-10-13 8:03 ` Jani Nikula
2017-10-12 20:23 ` [PATCH 4/8] Documentation: fix ref to coccinelle content Tom Saeger
2017-10-12 20:23 ` [PATCH 5/8] Documentation: fix ref to trace stm content Tom Saeger
2017-10-12 20:24 ` [PATCH 6/8] Documentation: fix ref to power basic-pm-debugging Tom Saeger
2017-10-12 20:46 ` Rafael J. Wysocki
2017-10-12 20:24 ` [PATCH 7/8] Documentation: fix selftests related file refs Tom Saeger
2017-10-20 16:53 ` Jerry Hoemann
2017-10-22 16:23 ` [7/8] " Guenter Roeck
2017-10-12 20:24 ` [PATCH 8/8] Documentation: fix ref to gpio.txt Tom Saeger
2017-10-16 12:03 ` Linus Walleij
2017-10-19 18:59 ` 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=20171019125915.0ad331e1@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.saeger@oracle.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 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.