From: Randy Dunlap <randy.dunlap@oracle.com>
To: Matt LaPlante <kernel1@cyberdogtech.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] Documentation cleanup: trivial misspelling, punctuation, and grammar corrections.
Date: Sun, 22 Jun 2008 20:25:39 -0700 [thread overview]
Message-ID: <20080622202539.f302ce03.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1214020821-19361-1-git-send-email-kernel1@cyberdogtech.com>
On Fri, 20 Jun 2008 23:00:21 -0500 Matt LaPlante wrote:
Signed-off-by: ??
A few nits below...
> diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
> index b7522c6..c4d348d 100644
> --- a/Documentation/filesystems/vfs.txt
> +++ b/Documentation/filesystems/vfs.txt
> @@ -895,9 +895,9 @@ struct dentry_operations {
> iput() yourself
>
> d_dname: called when the pathname of a dentry should be generated.
> - Usefull for some pseudo filesystems (sockfs, pipefs, ...) to delay
> + Useful for some pseudo filesystems (sockfs, pipefs, ...) to delay
> pathname generation. (Instead of doing it when dentry is created,
> - its done only when the path is needed.). Real filesystems probably
> + it's done only when the path is needed.). Real filesystems probably
> dont want to use it, because their dentries are present in global
don't
> dcache hash, so their hash should be an invariant. As no lock is
> held, d_dname() should not try to modify the dentry itself, unless
> diff --git a/Documentation/sound/alsa/Audiophile-Usb.txt b/Documentation/sound/alsa/Audiophile-Usb.txt
> index 2ad5e63..a4c53d8 100644
> --- a/Documentation/sound/alsa/Audiophile-Usb.txt
> +++ b/Documentation/sound/alsa/Audiophile-Usb.txt
> @@ -388,9 +388,9 @@ There are 2 main potential issues when using Jackd with the device:
>
> Jack supports big endian devices only in recent versions (thanks to
> Andreas Steinmetz for his first big-endian patch). I can't remember
> -extacly when this support was released into jackd, let's just say that
> +exactly when this support was released into jackd, let's just say that
> with jackd version 0.103.0 it's almost ok (just a small bug is affecting
> -16bits Big-Endian devices, but since you've read carefully the above
> +16bits Big-Endian devices, but since you've read carefully the above
16-bit (above and below here)
> paragraphs, you're now using kernel >= 2.6.23 and your 16bits devices
> are now Little Endians ;-) ).
>
Thanks. Big ack for all of the others.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
next prev parent reply other threads:[~2008-06-23 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 4:00 Matt LaPlante
2008-06-23 3:25 ` Randy Dunlap [this message]
2008-06-23 17:13 ` Matt LaPlante
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=20080622202539.f302ce03.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=kernel1@cyberdogtech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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®