mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt LaPlante <laplam@rpi.edu>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: [PATCH] Kconfig: Typos in fs/Kconfig
Date: Thu, 29 Jun 2006 03:24:54 -0400	[thread overview]
Message-ID: <20060629032454.f5e941f7.laplam@rpi.edu> (raw)
In-Reply-To: <20060629002036.ef53a483.rdunlap@xenotime.net>

On Thu, 29 Jun 2006 00:20:36 -0700
"Randy.Dunlap" <rdunlap@xenotime.net> wrote:

> On Thu, 29 Jun 2006 02:00:52 -0400 Matt LaPlante wrote:
> 
> > Fix several typos in fs/Kconfig
> > 
> > -
> > --- b/fs/Kconfig	2006-06-29 01:35:36.000000000 -0400
> > +++ a/fs/Kconfig	2006-06-29 01:58:52.000000000 -0400
> > @@ -69,7 +69,7 @@
> >  	default y
> >  
> >  config EXT3_FS
> > -	tristate "Ext3 journalling file system support"
> > +	tristate "Ext3 journaling file system support"
> 
> Some dictionaries spell it either way, but it should be spelled
> consistently (see 3 lines below).

You are correct, I went with the above since it did appear below and was the default in my references.  We can always swap and change the below.

> 
> >  	select JBD
> >  	help
> >  	  This is the journaling version of the Second extended file system
> 
> > @@ -1059,13 +1059,13 @@
> >  	  to be made available to the user in the /proc/fs/jffs/ directory.
> >  
> >  config JFFS2_FS
> > -	tristate "Journalling Flash File System v2 (JFFS2) support"
> > +	tristate "Journaling Flash File System v2 (JFFS2) support"
> >  	select CRC32
> >  	depends on MTD
> >  	help
> > -	  JFFS2 is the second generation of the Journalling Flash File System
> > +	  JFFS2 is the second generation of the Journaling Flash File System
> >  	  for use on diskless embedded devices. It provides improved wear
> > -	  levelling, compression and support for hard links. You cannot use
> > +	  leveling, compression and support for hard links. You cannot use
> 
> either spelling is OK.

This was my error, I tried to use at least two sources for the others but in this case apparently my initial spell checker was ignorant and I forgot to check elsewhere.  Can be left as is.

> 
> >  	  this on normal block devices, only on 'MTD' devices.
> >  
> >  	  Further information on the design and implementation of JFFS2 is
> 
> ---
> ~Randy
> 

-
Matt


  reply	other threads:[~2006-06-29  7:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29  6:00 Matt LaPlante
2006-06-29  7:20 ` Randy.Dunlap
2006-06-29  7:24   ` Matt LaPlante [this message]
2006-06-29 12:09 ` Alan Cox
2006-06-29 17:15   ` Matt LaPlante
2006-06-29 21:59     ` Alan Cox

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=20060629032454.f5e941f7.laplam@rpi.edu \
    --to=laplam@rpi.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=zippel@linux-m68k.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®