From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 2/2] PM: docs: Delete the obsolete states.txt document
Date: Mon, 21 Aug 2017 15:03:38 +0200 [thread overview]
Message-ID: <6985690.1N6x2ErZCO@aspire.rjw.lan> (raw)
In-Reply-To: <32BE8644-E9C9-44C9-A2CD-D833CFB611C6@darmarit.de>
On Monday, August 21, 2017 9:39:17 AM CEST Markus Heiser wrote:
>
> > Am 20.08.2017 um 18:06 schrieb Rafael J. Wysocki <rjw@rjwysocki.net>:
> >
> > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > The Documentation/power/states.txt document is now redundant and
> > sonewhat outdated, so delete it.
> >
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > ---
> > Documentation/power/states.txt | 127 -----------------------------------------
> > 1 file changed, 127 deletions(-)
>
> strange, I tried to apply the series, 1/2 applied but with 2/2 I get a
> "sha1 information is lacking or useless", did I miss something?
You need to apply this on top of linux-next, as some changes are made to
states.txt in one of the pending PM commits.
Thanks,
Rafael
prev parent reply other threads:[~2017-08-21 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 16:03 [PATCH 0/2] PM: docs: High-level update of PM part of admin-guide Rafael J. Wysocki
2017-08-20 16:05 ` [PATCH 1/2] PM: docs: Describe high-level PM strategies and sleep states Rafael J. Wysocki
2017-08-20 18:23 ` Lukas Wunner
2017-08-21 0:51 ` Rafael J. Wysocki
2017-08-21 9:51 ` Markus Heiser
2017-08-21 11:59 ` Rafael J. Wysocki
2017-08-21 13:14 ` [PATCH v2 " Rafael J. Wysocki
2017-08-28 21:16 ` Rafael J. Wysocki
2017-08-20 16:06 ` [PATCH 2/2] PM: docs: Delete the obsolete states.txt document Rafael J. Wysocki
2017-08-21 7:39 ` Markus Heiser
2017-08-21 13:03 ` Rafael J. Wysocki [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=6985690.1N6x2ErZCO@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=markus.heiser@darmarit.de \
/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).