All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Komal Shah" <komal_shah802003@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: greg@kroah.com
Subject: [PATCH] debugfs: spelling fix
Date: Tue, 29 Aug 2006 15:26:30 +0530	[thread overview]
Message-ID: <1156845390.1676.269651325@webmail.messagingengine.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 192 bytes --]

Greg,

Just a single line spell-fix for debugfs.

---Komal Shah
http://komalshah.blogspot.com

-- 
http://www.fastmail.fm - One of many happy users:
  http://www.fastmail.fm/docs/quotes.html


[-- Attachment #2: 0001-debugfs-spelling-fix.patch --]
[-- Type: application/octet-stream, Size: 983 bytes --]

From nobody Mon Sep 17 00:00:00 2001
From: Komal Shah <komal_shah802003@yahoo.com>
Date: Tue, 29 Aug 2006 20:54:53 +0530
Subject: [PATCH] debugfs: spelling fix

Change debufs_create_file() to debugfs_create_file().

Signed-off-by: Komal Shah <komal_shah802003@yahoo.com>

---

 fs/debugfs/inode.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

fb57f4f63fddf334166f6a8130b41eae47b0da2e
diff --git a/fs/debugfs/inode.c b/fs/debugfs/inode.c
index e8ae304..ce8bf7c 100644
--- a/fs/debugfs/inode.c
+++ b/fs/debugfs/inode.c
@@ -256,7 +256,7 @@ EXPORT_SYMBOL_GPL(debugfs_create_dir);
  *
  * This function removes a file or directory in debugfs that was previously
  * created with a call to another debugfs function (like
- * debufs_create_file() or variants thereof.)
+ * debugfs_create_file() or variants thereof.)
  *
  * This function is required to be called in order for the file to be
  * removed, no automatic cleanup of files will happen when a module is
-- 
1.3.3


             reply	other threads:[~2006-08-29  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29  9:56 Komal Shah [this message]
2006-08-29 16:04 ` [PATCH] debugfs: spelling fix Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2006-08-30  5:30 Komal Shah
2006-08-30  5:38 ` Greg KH

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=1156845390.1676.269651325@webmail.messagingengine.com \
    --to=komal_shah802003@yahoo.com \
    --cc=greg@kroah.com \
    --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.