All of lore.kernel.org
 help / color / mirror / Atom feed
From: Siddaraju DH <siddarajudh@gmail.com>
To: john.stultz@linaro.org
Cc: tglx@linutronix.de, corbet@lwn.net, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, Siddaraju DH <siddarajudh@gmail.com>
Subject: [PATCH] timekeeping.txt: Correct maxCount of n-bit binary counter
Date: Thu, 19 Jul 2018 22:06:51 +0530	[thread overview]
Message-ID: <20180719163651.19360-1-siddarajudh@gmail.com> (raw)

A n-bit binary counter can count a maximum of 2^n events and the count
value ranges from 0 to (2^n)-1

Signed-off-by: Siddaraju DH <siddarajudh@gmail.com>
---
 Documentation/timers/timekeeping.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/timers/timekeeping.txt b/Documentation/timers/timekeeping.txt
index f3a8cf2..2d1732b 100644
--- a/Documentation/timers/timekeeping.txt
+++ b/Documentation/timers/timekeeping.txt
@@ -27,7 +27,7 @@ a Linux system will eventually read the clock source to determine exactly
 what time it is.
 
 Typically the clock source is a monotonic, atomic counter which will provide
-n bits which count from 0 to 2^(n-1) and then wraps around to 0 and start over.
+n bits which count from 0 to (2^n)-1 and then wraps around to 0 and start over.
 It will ideally NEVER stop ticking as long as the system is running. It
 may stop during system suspend.
 
-- 
2.7.4

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Siddaraju DH <siddarajudh@gmail.com>
To: john.stultz@linaro.org
Cc: tglx@linutronix.de, corbet@lwn.net, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, Siddaraju DH <siddarajudh@gmail.com>
Subject: [PATCH] timekeeping.txt: Correct maxCount of n-bit binary counter
Date: Thu, 19 Jul 2018 22:06:51 +0530	[thread overview]
Message-ID: <20180719163651.19360-1-siddarajudh@gmail.com> (raw)

A n-bit binary counter can count a maximum of 2^n events and the count
value ranges from 0 to (2^n)-1

Signed-off-by: Siddaraju DH <siddarajudh@gmail.com>
---
 Documentation/timers/timekeeping.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/timers/timekeeping.txt b/Documentation/timers/timekeeping.txt
index f3a8cf2..2d1732b 100644
--- a/Documentation/timers/timekeeping.txt
+++ b/Documentation/timers/timekeeping.txt
@@ -27,7 +27,7 @@ a Linux system will eventually read the clock source to determine exactly
 what time it is.
 
 Typically the clock source is a monotonic, atomic counter which will provide
-n bits which count from 0 to 2^(n-1) and then wraps around to 0 and start over.
+n bits which count from 0 to (2^n)-1 and then wraps around to 0 and start over.
 It will ideally NEVER stop ticking as long as the system is running. It
 may stop during system suspend.
 
-- 
2.7.4


             reply	other threads:[~2018-07-19 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 16:36 Siddaraju DH [this message]
2018-07-19 16:36 ` [PATCH] timekeeping.txt: Correct maxCount of n-bit binary counter Siddaraju DH
2018-07-23 15:33 ` Jonathan Corbet
2018-07-23 15:33   ` Jonathan Corbet

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=20180719163651.19360-1-siddarajudh@gmail.com \
    --to=siddarajudh@gmail.com \
    --cc=corbet@lwn.net \
    --cc=john.stultz@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.