mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Otto Sabart <ottosabart@seberm.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Jonathan Corbet <corbet@lwn.net>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH 1/1] doc: trace: fix reference to cpuidle documentation file
Date: Wed, 09 Jan 2019 11:45:09 +0100	[thread overview]
Message-ID: <3605332.KXf7BibVrA@aspire.rjw.lan> (raw)
In-Reply-To: <f9650f8f9d085a47caf3db1baa41310d6646ae00.1546991610.git.ottosabart@seberm.com>

On Wednesday, January 9, 2019 12:56:51 AM CET Otto Sabart wrote:
> 
> --LZvS9be/3tNcYl/X
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> Old cpuidle/sysfs.txt file was replaced in aa5eee355b46. So, refer to
> an updated file.
> 
> Fixes: aa5eee355b46 ("Documentation: admin-guide: PM: Add cpuidle document")
> Signed-off-by: Otto Sabart <ottosabart@seberm.com>
> ---
>  Documentation/trace/coresight-cpu-debug.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/trace/coresight-cpu-debug.txt b/Documentation/tr=
> ace/coresight-cpu-debug.txt
> index 89ab09e78e8d..f07e38094b40 100644
> --- a/Documentation/trace/coresight-cpu-debug.txt
> +++ b/Documentation/trace/coresight-cpu-debug.txt
> @@ -165,7 +165,7 @@ Do some work...
>  The same can also be done from an application program.
> =20
>  Disable specific CPU's specific idle state from cpuidle sysfs (see
> -Documentation/cpuidle/sysfs.txt):
> +Documentation/admin-guide/pm/cpuidle.rst):
>  # echo 1 > /sys/devices/system/cpu/cpu$cpu/cpuidle/state$state/disable

Applied, thanks!


      reply	other threads:[~2019-01-09 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 23:56 Otto Sabart
2019-01-09 10:45 ` 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=3605332.KXf7BibVrA@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=ottosabart@seberm.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=suzuki.poulose@arm.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®