mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Peter Huewe <peterhuewe@gmx.de>
Cc: Greg KH <gregkh@suse.de>,
	devel@linuxdriverproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging/trivial: Fix common spelling mistakes
Date: Mon, 14 Mar 2011 15:03:13 -0700	[thread overview]
Message-ID: <20110314220313.GA21204@kroah.com> (raw)
In-Reply-To: <1300139875-8688-1-git-send-email-peterhuewe@gmx.de>

On Mon, Mar 14, 2011 at 10:57:55PM +0100, Peter Huewe wrote:
> This patch fixes some very common spelling mistakes in drivers/staging
> The changes were carried out by hand and are made in
> documentation/comments only - no functional change.
> Variables were left untouched on purpose.
> Linebreaks were also left untouched on purpose.
> 
> The fixed spelling mistakes are:
> WRONG -> RIGHT
> 
> accomodate -> accommodate
> acommodate -> accommodate
> 
> adress -> address
> addres -> address
> 
> hightest -> highest
> hight -> height
> hight -> high (when mentioned in contrast to low)
> hightlight -> highlight
> 
> libary -> library
> libaray -> library
> 
> occured -> occurred
> 
> reqest -> request
> reguest -> request
> requst -> request
> reqeust -> request
> 
> acheive -> achieve
> beggining -> beginning
> embarass -> embarrass
> enviroment -> environment
> fagment -> fragment
> indefinately-> indefinitely
> knowlege -> knowledge
> regester -> register
> unferflow -> underflow
> 
> recieve -> receive
> 
> interupt -> interrupt
> interrrupt -> interrupt
> 
> paralell -> parallel
> paralel -> parallel
> preceeding -> preceding
> publically -> publicly
> shedule -> shedule
> supercede -> supersede
> wierd -> weird
> writen -> written
> writting -> writing
> 
> And some other minor changes that caught my eye doing the changes
> 
> KernelVersion: Linux-next of 20110314 (c0ebee1a2)

Unfortunatly, I've applied a bunch of patches since the last linux-next
tree.

It would be nice if I could have taken a bunch of these changes, and if
it was broken up into individual patches (each either doing only one
spelling change, or only operating on one driver/file) then I could
have.  But as it is, I can't :(

So, another reason it makes sense to break patches up into the logical
pieces.  Please do this and resend.

thanks,

greg k-h

  reply	other threads:[~2011-03-14 22:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 13:18 [PATCH] trivial: fix " Peter Huewe
2011-01-06 14:01 ` Jesper Juhl
2011-01-06 14:14   ` Peter Hüwe
2011-01-07 10:04 ` Jiri Kosina
2011-01-07 13:38   ` Peter Hüwe
2011-03-08 22:49   ` [PATCH v2/resend] " Peter Huewe
2011-03-14 12:00     ` Jiri Kosina
2011-03-14 20:35       ` [PATCH v3] " Peter Huewe
2011-03-14 21:57       ` [PATCH] staging/trivial: Fix " Peter Huewe
2011-03-14 22:03         ` Greg KH [this message]
2011-03-14 22:43           ` Peter Hüwe
2011-03-14 22:47             ` Greg KH
2011-03-26  1:17               ` [PATCH 0/27] " Peter Huewe
2011-03-26  1:17               ` [PATCH 01/27] staging/ath6kl: " Peter Huewe
2011-03-26  1:17               ` [PATCH 02/27] staging/bcm: " Peter Huewe
2011-03-26  1:17               ` [PATCH 03/27] staging/brcm80211: " Peter Huewe
2011-03-26  1:17               ` [PATCH 04/27] staging/comedi: " Peter Huewe
2011-03-26  1:17               ` [PATCH 05/27] staging/crystalhd: " Peter Huewe
2011-03-26  1:17               ` [PATCH 06/27] staging/dt3155v4l: " Peter Huewe
2011-03-26  1:17               ` [PATCH 07/27] staging/easycap: " Peter Huewe
2011-03-15  3:14         ` [PATCH] staging/trivial: " Harry Wei
2011-03-26  1:39           ` Peter Hüwe
2011-03-26  2:21             ` Harry Wei
2011-03-15  2:58     ` [PATCH v2/resend] trivial: fix " Harry Wei

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=20110314220313.GA21204@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    /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

Powered by JetHome