public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Fernando Carrijo <fcarrijo@yahoo.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix similar typos to successfull, v2
Date: Tue, 25 Nov 2008 16:05:24 -0800	[thread overview]
Message-ID: <20081125160524.102a2b3a.akpm@linux-foundation.org> (raw)
In-Reply-To: <1227656953.18268.13.camel@pc-fernando>

On Tue, 25 Nov 2008 21:49:13 -0200
Fernando Carrijo <fcarrijo@yahoo.com.br> wrote:

> On Tue, 2008-11-25 at 14:53 -0800, Andrew Morton wrote:
> > On Tue, 25 Nov 2008 01:44:13 +0800
> > Coly Li <coyli@suse.de> wrote:
> > 
> > > When I review ocfs2 code, find there are 2 typos to "successfull". After doing grep "successfull "
> > > in kernel tree, 22 typos found totally --  great minds always think alike  :)
> > 
> > Mutter.  I have a super-strict (lol) policy of "I don't take patches
> > which fix typos/spellos in comments", because we have so many such
> > errors, and I'd get buried in silly patches.  But I do take patches
> > which fix documentation and user-visible printks, etc.
> 
> Since you started the thread, I feel less guilty to talk about the
> existence of tons of another kind of typo spread around the kernel
> sources: null statements created by duplicated semi-colons at the end of
> statements. Something like foo();;

We should just fix those.

  reply	other threads:[~2008-11-26  0:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 17:44 [PATCH] fix similar typos to successfull, v2 Coly Li
2008-11-24 17:40 ` Randy Dunlap
2008-11-25 22:53 ` Andrew Morton
2008-11-25 23:49   ` Fernando Carrijo
2008-11-26  0:05     ` Andrew Morton [this message]
2008-11-26  0:42       ` Fernando Carrijo
2008-11-26  8:48   ` Coly Li

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=20081125160524.102a2b3a.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=fcarrijo@yahoo.com.br \
    --cc=linux-kernel@vger.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