From: Randy Dunlap <rdunlap@xenotime.net>
To: Sylvestre Ledru <sylvestre.ledru@scilab.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix some minor typos: * informations => information * there own => their own * an => and (bug #14973)
Date: Sat, 26 Mar 2011 10:29:05 -0700 [thread overview]
Message-ID: <20110326102905.bae3c800.rdunlap@xenotime.net> (raw)
In-Reply-To: <1301010464-22583-1-git-send-email-sylvestre.ledru@scilab.org>
On Fri, 25 Mar 2011 00:47:44 +0100 Sylvestre Ledru wrote:
Hi,
This patch is mostly good, with a few exceptions as noted below.
Please resend a complete corrected patch.
> Signed-off-by: Sylvestre Ledru <sylvestre.ledru@scilab.org>
> ---
> .../ABI/testing/sysfs-driver-hid-roccat-kone | 2 +-
> .../ABI/testing/sysfs-driver-hid-roccat-koneplus | 8 ++++----
> .../ABI/testing/sysfs-driver-hid-roccat-kovaplus | 8 ++++----
> .../ABI/testing/sysfs-driver-hid-roccat-pyra | 8 ++++----
> .../ABI/testing/sysfs-platform-asus-laptop | 2 +-
> Documentation/devicetree/booting-without-of.txt | 6 +++---
> Documentation/dvb/udev.txt | 2 +-
> Documentation/edac.txt | 2 +-
> Documentation/kernel-parameters.txt | 4 ++--
> Documentation/laptops/asus-laptop.txt | 4 ++--
> Documentation/networking/batman-adv.txt | 2 +-
> Documentation/s390/Debugging390.txt | 2 +-
> Documentation/scsi/sym53c8xx_2.txt | 2 +-
> Documentation/sound/alsa/ALSA-Configuration.txt | 2 +-
> Documentation/sound/oss/AudioExcelDSP16 | 6 +++---
> Documentation/sound/oss/README.ymfsb | 2 +-
> Documentation/video4linux/bttv/Insmod-options | 2 +-
> Documentation/video4linux/bttv/Sound-FAQ | 2 +-
> Documentation/video4linux/et61x251.txt | 4 ++--
> Documentation/video4linux/sn9c102.txt | 4 ++--
> Documentation/video4linux/w9968cf.txt | 2 +-
> Documentation/video4linux/zc0301.txt | 6 +++---
> arch/powerpc/mm/tlb_low_64e.S | 2 +-
> arch/powerpc/platforms/Kconfig | 2 +-
> fs/notify/fanotify/Kconfig | 2 +-
> 25 files changed, 44 insertions(+), 44 deletions(-)
> diff --git a/Documentation/ABI/testing/sysfs-platform-asus-laptop b/Documentation/ABI/testing/sysfs-platform-asus-laptop
> index 41ff8ae..01160d8 100644
> --- a/Documentation/ABI/testing/sysfs-platform-asus-laptop
> +++ b/Documentation/ABI/testing/sysfs-platform-asus-laptop
> @@ -27,7 +27,7 @@ KernelVersion: 2.6.20
> Contact: "Corentin Chary" <corentincj@iksaif.net>
> Description:
> Some models like the W1N have a LED display that can be
an
> - used to display several informations.
> + used to display several information.
Either way is awkward. Needs something more like:
used to display several items of information.
> To control the LED display, use the following :
> echo 0x0T000DDD > /sys/devices/platform/asus_laptop/
> where T control the 3 letters display, and DDD the 3 digits display.
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index d18a9e1..29ac507 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -2463,8 +2463,8 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
> topology= [S390]
> Format: {off | on}
> Specify if the kernel should make use of the cpu
> - topology informations if the hardware supports these.
> - The scheduler will make use of these informations and
> + topology information if the hardware supports these.
s/these/this/ just as was done below.
> + The scheduler will make use of this information and
> e.g. base its process migration decisions on it.
> Default is on.
>
> diff --git a/Documentation/laptops/asus-laptop.txt b/Documentation/laptops/asus-laptop.txt
> index c1c5be8..90d8b86 100644
> --- a/Documentation/laptops/asus-laptop.txt
> +++ b/Documentation/laptops/asus-laptop.txt
> @@ -178,7 +178,7 @@ LED display
> -----------
>
> Some models like the W1N have a LED display that can be used to display
> - several informations.
> + several information.
Same comment as above.
>
> LED display works for the following models:
> W1000N
> diff --git a/fs/notify/fanotify/Kconfig b/fs/notify/fanotify/Kconfig
> index 7dceff0..30dc09c 100644
> --- a/fs/notify/fanotify/Kconfig
> +++ b/fs/notify/fanotify/Kconfig
> @@ -6,7 +6,7 @@ config FANOTIFY
> ---help---
> Say Y here to enable fanotify suport. fanotify is a file access
> notification system which differs from inotify in that it sends
> - an open file descriptor to the userspace listener along with
> + and opens file descriptor to the userspace listener along with
Nope, "an open" is correct.
> the event.
>
> If unsure, say Y.
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-03-26 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 23:47 Sylvestre Ledru
2011-03-26 17:29 ` Randy Dunlap [this message]
2011-03-26 19:22 ` Sylvestre Ledru
2011-03-28 15:54 ` Randy Dunlap
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=20110326102905.bae3c800.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sylvestre.ledru@scilab.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®