All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH][TRIVIAL] Fix comments in 2.6.16-rc6: s/granuality/granularity/
Date: Mon, 13 Mar 2006 05:39:24 +0900	[thread overview]
Message-ID: <dv20tt$46a$1@sea.gmane.org> (raw)

Hi there,
I was grepping through the code and some `grep ganularity -R .` didn't
catch what I thought. Then looking closer I saw the term "granuality"
used in only four places (in comments) and granularity in many more
places describing the same idea. Some other facts:

dictionary.com does not know such a word
define:granuality on google is not found (and pages for granuality are
mostly related to patches to the kernel)
it has not been discussed as a term on LKML, AFAICS (=Can Search)

To be consistent, I think granularity should be used everywhere.

Here is the patch for the latest 2.6.16-rc6.
All trivial, all comments only, not "affecting kernel stability".
If somebody can take care to push it for rc7, if not for later.

I reading LKML, but please CC me if you decide to to (not) accept it.

Kalin.
-- 
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|

Signed-off-by: Kalin KOZHUHAROV <kalin@thinrope.net>

diff -Nru linux-2.6.16-rc6-V/include/linux/fs.h linux-2.6.16-rc6-K/include/linux/fs.h
--- linux-2.6.16-rc6-V/include/linux/fs.h	2006-03-13 03:04:36.000000000 +0900
+++ linux-2.6.16-rc6-K/include/linux/fs.h	2006-03-13 03:12:46.000000000 +0900
@@ -849,7 +849,7 @@
 	 */
 	struct semaphore s_vfs_rename_sem;	/* Kludge */
 
-	/* Granuality of c/m/atime in ns.
+	/* Granularity of c/m/atime in ns.
 	   Cannot be worse than a second */
 	u32		   s_time_gran;
 };
diff -Nru linux-2.6.16-rc6-V/kernel/time.c linux-2.6.16-rc6-K/kernel/time.c
--- linux-2.6.16-rc6-V/kernel/time.c	2006-03-13 03:04:40.000000000 +0900
+++ linux-2.6.16-rc6-K/kernel/time.c	2006-03-13 03:11:58.000000000 +0900
@@ -437,7 +437,7 @@
  * current_fs_time - Return FS time
  * @sb: Superblock.
  *
- * Return the current time truncated to the time granuality supported by
+ * Return the current time truncated to the time granularity supported by
  * the fs.
  */
 struct timespec current_fs_time(struct super_block *sb)
@@ -448,11 +448,11 @@
 EXPORT_SYMBOL(current_fs_time);
 
 /**
- * timespec_trunc - Truncate timespec to a granuality
+ * timespec_trunc - Truncate timespec to a granularity
  * @t: Timespec
- * @gran: Granuality in ns.
+ * @gran: Granularity in ns.
  *
- * Truncate a timespec to a granuality. gran must be smaller than a second.
+ * Truncate a timespec to a granularity. gran must be smaller than a second.
  * Always rounds down.
  *
  * This function should be only used for timestamps returned by



                 reply	other threads:[~2006-03-12 21:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='dv20tt$46a$1@sea.gmane.org' \
    --to=kalin@thinrope.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 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.