From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH 0/4] Documentation: PM: Assorted updates
Date: Mon, 8 Apr 2019 11:46:04 +0530 [thread overview]
Message-ID: <20190408061604.vezucnff4dp2tx7x@vireshk-i7> (raw)
In-Reply-To: <4546107.fVFrecLk33@aspire.rjw.lan>
On 04-04-19, 00:02, Rafael J. Wysocki wrote:
> Hi All,
>
> There patches make some changes in the PM documentation:
>
> - Add "references" sections to cpufreq-related documents (patch [1/4]).
> - Add SPDX license tags to multiple PM-related documents (patch [2/4]).
> - Unify copyright notices in PM-related documents (patch [3/4]).
> - Add an SPDX license tag and a copyright notice to the new
> intel_epb doc (in linux-next only ATM).
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
prev parent reply other threads:[~2019-04-08 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 22:02 Rafael J. Wysocki
2019-04-03 22:03 ` [PATCH 1/4] cpufreq: intel_pstate: Documentation: Add references sections Rafael J. Wysocki
2019-04-03 22:04 ` [PATCH 2/4] Documentation: PM: Add SPDX license tags to multiple files Rafael J. Wysocki
2019-04-03 22:06 ` [PATCH 3/4] Documentation: PM: Unify copyright notices Rafael J. Wysocki
2019-04-03 22:08 ` [PATCH 4/4] admin-guide: pm: intel_epb: Add SPDX license tag and copyright notice Rafael J. Wysocki
2019-04-08 6:16 ` Viresh Kumar [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=20190408061604.vezucnff4dp2tx7x@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=corbet@lwn.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.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®