linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: y@vger.kernel.org
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>,
	Sergei Trofimovich <slyfox@gentoo.org>
Subject: [PATCH v2 2/3] btrfs: typo: 'btrfS' -> 'btrfs'
Date: Tue, 10 May 2011 22:57:28 +0300	[thread overview]
Message-ID: <1305057449-12075-3-git-send-email-y> (raw)
In-Reply-To: <1305057449-12075-1-git-send-email-y>

From: Sergei Trofimovich <slyfox@gentoo.org>

Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
---
 fs/btrfs/dir-item.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/fs/btrfs/dir-item.c b/fs/btrfs/dir-item.c
index c62f02f..dec9348 100644
--- a/fs/btrfs/dir-item.c
+++ b/fs/btrfs/dir-item.c
@@ -452,7 +452,7 @@ int verify_dir_item(struct btrfs_root *root,
 		namelen = XATTR_NAME_MAX;
 
 	if (btrfs_dir_name_len(leaf, dir_item) > namelen) {
-		printk(KERN_CRIT "btrfS: invalid dir item name len: %u\n",
+		printk(KERN_CRIT "btrfs: invalid dir item name len: %u\n",
 		       (unsigned)btrfs_dir_data_len(leaf, dir_item));
 		return 1;
 	}
-- 
1.7.3.4


  parent reply	other threads:[~2011-05-10 19:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 19:57 [PATCH v2 0/3] btrfs: don't spin in shrink_delalloc if there is nothing to free y
2011-05-10 19:57 ` [PATCH v2 1/3] " y
2011-05-10 19:57 ` y
2011-05-10 19:57 ` [PATCH v2 2/3] btrfs: typo: 'btrfS' -> 'btrfs' y
2011-05-10 19:57 ` y [this message]
2011-05-10 19:57 ` [PATCH v2 3/3] btrfs: fix typo 'testeing' -> 'testing' y
2011-05-10 19:57 ` y
  -- strict thread matches above, loose matches on Subject: below --
2011-05-10 20:01 [PATCH v2 0/3] btrfs: don't spin in shrink_delalloc if there is nothing to free Sergei Trofimovich
2011-05-10 20:01 ` [PATCH v2 2/3] btrfs: typo: 'btrfS' -> 'btrfs' Sergei Trofimovich

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=1305057449-12075-3-git-send-email-y \
    --to=y@vger.kernel.org \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=slyfox@gentoo.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;
as well as URLs for NNTP newsgroup(s).