From: "Will Newton" <will.newton@gmail.com>
To: "Jonathan Corbet" <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Pull] Some documentation patches
Date: Fri, 28 Mar 2008 19:39:17 +0000 [thread overview]
Message-ID: <87a5b0800803281239q43cd708ay7351c097f6368c3e@mail.gmail.com> (raw)
In-Reply-To: <13387.1206728412@vena.lwn.net>
On Fri, Mar 28, 2008 at 6:20 PM, Jonathan Corbet <corbet@lwn.net> wrote:
> I've noticed that getting documentation patches merged seems to be a
> slower and more uncertain process than it was a while back. So I
> figured I'd try to be one of the cool folks with their own git tree and
> see if that works better. Linus, if you agree, could you please pull:
A small patch for the highres timers documentation:
Signed-off-by: Will newton <will.newton@gmail.com>
---
Documentation/hrtimers/highres.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/hrtimers/highres.txt
b/Documentation/hrtimers/highres.txt
index ce0e9a9..a73ecf5 100644
--- a/Documentation/hrtimers/highres.txt
+++ b/Documentation/hrtimers/highres.txt
@@ -98,7 +98,7 @@ System-level global event devices are used for the
Linux periodic tick. Per-CPU
event devices are used to provide local CPU functionality such as process
accounting, profiling, and high resolution timers.
-The management layer assignes one or more of the folliwing functions to a clock
+The management layer assigns one or more of the following functions to a clock
event device:
- system global periodic tick (jiffies update)
- cpu local update_process_times
--
1.5.4.3
next prev parent reply other threads:[~2008-03-28 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 18:20 Jonathan Corbet
2008-03-28 18:28 ` Jan Engelhardt
2008-03-28 18:34 ` Linus Torvalds
2008-03-28 18:36 ` Jonathan Corbet
2008-03-28 19:09 ` Jan Engelhardt
2008-03-28 19:22 ` Jonathan Corbet
2008-03-31 14:31 ` Dmitri Vorobiev
2008-04-01 20:00 ` Jan Engelhardt
2008-03-28 19:39 ` Will Newton [this message]
2008-03-28 19:47 ` Randy Dunlap
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=87a5b0800803281239q43cd708ay7351c097f6368c3e@mail.gmail.com \
--to=will.newton@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.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®