public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: "Raoul Bhatia [IPAX]" <r.bhatia@ipax.at>
Cc: "trivial@kernel.org" <trivial@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] trivial: fix typos in Documentation/edac.txt and Documentation/filesystems/ext4.txt
Date: Mon, 10 Oct 2011 19:59:05 +0200	[thread overview]
Message-ID: <20111010175905.GB29415@aftab> (raw)
In-Reply-To: <4E931F78.7050007@ipax.at>

On Mon, Oct 10, 2011 at 12:38:16PM -0400, Raoul Bhatia [IPAX] wrote:
> Fixing trivial typos in
> Documentation/edac.txt and
> Documentation/filesystems/ext4.txt
> 
> patch for current git head checkout from
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> 
> Signed-off-by: Raoul Bhatia <r.bhatia@ipax.at>
> ---
> diff --git a/Documentation/edac.txt b/Documentation/edac.txt
> index 249822c..8ba7bb4 100644
> --- a/Documentation/edac.txt
> +++ b/Documentation/edac.txt
> @@ -643,7 +643,7 @@ There is a three level tree beneath the above 'edac' 
> directory. For example,
>   the 'test_device_edac' device (found at the bluesmoke.sourceforget.net 
> website)
>   installs itself as:
> 
> -	/sys/devices/systm/edac/test-instance
> +	/sys/devices/system/edac/test-instance
> 
>   in this directory are various controls, a symlink and one or more 
> 'instance'
>   directorys.
> diff --git a/Documentation/filesystems/ext4.txt 
> b/Documentation/filesystems/ext4.txt
> index 232a575..a8356c3 100644
> --- a/Documentation/filesystems/ext4.txt
> +++ b/Documentation/filesystems/ext4.txt
> @@ -352,7 +352,7 @@ noinit_itable		Do not initialize any uninitialized 
> inode table
>   init_itable=n		The lazy itable init code will wait n times the
>   			number of milliseconds it took to zero out the
>   			previous block group's inode table.  This
> -			minimizes the impact on the systme performance
> +			minimizes the impact on the system performance
>   			while file system's inode table is being initialized.
> 
>   discard			Controls whether ext4 should issue discard/TRIMa

Right, a couple of suggestions:

* please don't mix different subsystems in a single patch: EDAC should be one
patch and fs another.

* Documentation/edac.txt is pretty old and has more errors than this one
so it would be much better to create a single patch which scrubs that
file properly and thoroughly.

Also, while you're at it, please run the driver and verify that all the
functionality described there actually works and document any changes
you might find which are deviating from the document. And if anything is
broken, you might even try to fix it, if you'd like :-) - patches are
always welcome.

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551

      reply	other threads:[~2011-10-10 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111010163245.B6B4B281C28@ip52.ipax.at>
2011-10-10 16:38 ` [PATCH] trivial: fix typos in Documentation/edac.txt and Documentation/filesystems/ext4.txt Raoul Bhatia [IPAX]
2011-10-10 17:59   ` Borislav Petkov [this message]

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=20111010175905.GB29415@aftab \
    --to=bp@amd64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=r.bhatia@ipax.at \
    --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