From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PM <linux-pm@vger.kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Linux Documentation <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Subject: [PATCH 0/3] PM / docs: linux/pm.h kerneldocs update and conversion of two docs to reST
Date: Fri, 06 Jan 2017 02:38:13 +0100 [thread overview]
Message-ID: <17467778.bsRBpnPicc@aspire.rjw.lan> (raw)
Hi Everyone,
I sent patches [1-2/3] previosly a couple of weeks ago and there have not been
any comments since then, so either they are fine by everybody or the timing
was particularly bad and no one had the time to look at them. Admittedly, the
former is more attractive to me, so I'll assume that this is the case if there
are no comments still this time. :-)
Patch [1/3] updates kerneldoc comments in include/linux/pm.h (to make the
documentation generated out of them look better), patch [2/3] converts
Documentation/power/devices.txt to reST, and patch [3/3] does the same thing
to Documentation/power/notifiers.txt (the new files go into the driver-api subdir
and are hooked up to that manual).
If the conversions can be done in a better way (with not much more effort),
please let me know.
Thanks,
Rafael
next reply other threads:[~2017-01-06 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 1:38 Rafael J. Wysocki [this message]
2017-01-06 1:39 ` [Resend][PATCH 1/3] PM / core: Update kerneldoc comments in pm.h Rafael J. Wysocki
2017-01-06 1:41 ` [Resend][PATCH 2/3] PM / core / docs: Convert sleep states API document to reST Rafael J. Wysocki
2017-01-10 1:41 ` Lukas Wunner
2017-01-11 2:58 ` Rafael J. Wysocki
2017-01-06 1:44 ` [PATCH 3/3] PM / sleep / docs: Convert PM notifiers " Rafael J. Wysocki
2017-01-09 1:34 ` [PATCH 0/3] PM / docs: linux/pm.h kerneldocs update and conversion of two docs " Lukas Wunner
2017-02-02 0:06 ` Rafael J. Wysocki
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=17467778.bsRBpnPicc@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@osg.samsung.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
all inboxes | Powered by JetHome®