mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: trivial@kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Justin P. Mattock" <justinmattock@gmail.com>
Subject: [PATCH 89/89]Documentation/power/basic-pm-debugging.txt update web address
Date: Tue, 20 Jul 2010 21:55:52 -0700	[thread overview]
Message-ID: <1279688153-29571-14-git-send-email-justinmattock@gmail.com> (raw)
In-Reply-To: <1279688153-29571-1-git-send-email-justinmattock@gmail.com>

The patch below updates a broken web address.

Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>

---
 Documentation/power/basic-pm-debugging.txt |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/Documentation/power/basic-pm-debugging.txt b/Documentation/power/basic-pm-debugging.txt
index 1555001..ddd7817 100644
--- a/Documentation/power/basic-pm-debugging.txt
+++ b/Documentation/power/basic-pm-debugging.txt
@@ -179,8 +179,7 @@ use the PM_TRACE mechanism documented in Documentation/s2ram.txt .
 
 To verify that the STR works, it is generally more convenient to use the s2ram
 tool available from http://suspend.sf.net and documented at
-http://en.opensuse.org/s2ram .  However, before doing that it is recommended to
-carry out STR testing using the facility described in section 1.
+http://en.opensuse.org/SDB:Suspend_to_RAM.
 
 Namely, after writing "freezer", "devices", "platform", "processors", or "core"
 into /sys/power/pm_test (available if the kernel is compiled with
-- 
1.7.1.rc1.21.gf3bd6


  parent reply	other threads:[~2010-07-21  5:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21  4:55 [PATCH 76/76]Documentation/networking/fore200e.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 77/77]Documentation/networking/tlan.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 78/78]Documentation/networking/arcnet.txt update web addresses Justin P. Mattock
2010-07-21  4:55 ` [PATCH 79/79]Documentation/networking/udplite.txt update web address Justin P. Mattock
2010-07-21  4:55 ` [PATCH 80/80]Documentation/networking/README.ipw2200 " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 81/81]Documentation/networking/3c509.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 82/82]Documentation/networking/s2io.txt update wbe address Justin P. Mattock
2010-07-21  9:05   ` Thomas Weber
2010-07-21 13:34     ` Justin P. Mattock
2010-07-21  4:55 ` [PATCH 83/83]Documentation/networking/packet_mmap.txt update web address Justin P. Mattock
2010-07-21  4:55 ` [PATCH 84/84]Documentation/networking/ipddp.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 85/85]Documentation/networking/README.ipw2100 " Justin P. Mattock
2010-07-21  9:16   ` Thomas Weber
2010-07-21 13:32     ` Justin P. Mattock
2010-07-21  4:55 ` [PATCH 86/86]Documentation/networking/README.sb1000 " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 87/87]Documentation/networking/wavelan.txt " Justin P. Mattock
2010-07-21  4:55 ` [PATCH 88/88]Documentation/networking/ray_cs.txt " Justin P. Mattock
2010-07-21  4:55 ` Justin P. Mattock [this message]
2010-07-21  4:55 ` [PATCH 90/90]Documentation/power/video.txt " Justin P. Mattock

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=1279688153-29571-14-git-send-email-justinmattock@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.org \
    /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®