From: "Oliver Pinter (Pintér Olivér)" <oliver.pntr@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [06/06] [typo fix] Documentation/filesystems/porting
Date: Sun, 30 Dec 2007 14:20:54 +0100 [thread overview]
Message-ID: <6101e8c40712300520r7c702bc9o7411317c2d10cd25@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 19 bytes --]
--
Thanks,
Oliver
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 06.patch --]
[-- Type: text/x-diff; name=06.patch, Size: 1228 bytes --]
commit 93d021f12d5370d06b1eee0659d83d1e7095df6c
Author: Oliver Pinter <oliver.pntr@gmail.com>
Commit: Oliver Pinter <oliver.pntr@gmail.com>
[typo fix] Documentation/filesystems/porting
typo fix in Documentation/filesystems/porting
foo-destory -> foo-destroy && whitespace cleanup
Signed-off-by: Oliver Pinter <oliver.pntr@gmail.com>
diff --git a/Documentation/filesystems/porting b/Documentation/filesystems/porting
index dac45c9..0f33c77 100644
--- a/Documentation/filesystems/porting
+++ b/Documentation/filesystems/porting
@@ -1,6 +1,6 @@
Changes since 2.5.0:
----
+---
[recommended]
New helpers: sb_bread(), sb_getblk(), sb_find_get_block(), set_bh(),
@@ -10,7 +10,7 @@ Use them.
(sb_find_get_block() replaces 2.4's get_hash_table())
----
+---
[recommended]
New methods: ->alloc_inode() and ->destroy_inode().
@@ -28,7 +28,7 @@ Declare
Use FOO_I(inode) instead of &inode->u.foo_inode_i;
-Add foo_alloc_inode() and foo_destory_inode() - the former should allocate
+Add foo_alloc_inode() and foo_destroy_inode() - the former should allocate
foo_inode_info and return the address of ->vfs_inode, the latter should free
FOO_I(inode) (see in-tree filesystems for examples).
reply other threads:[~2007-12-30 13:21 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=6101e8c40712300520r7c702bc9o7411317c2d10cd25@mail.gmail.com \
--to=oliver.pntr@gmail.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 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®