public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Fix typos
Date: Thu, 02 Sep 2010 13:13:13 -0700	[thread overview]
Message-ID: <4C800559.10701@oracle.com> (raw)
In-Reply-To: <AANLkTineHC5C=Sv5uZezx7-RF3_rQOJFBePhfzD6jfMF@mail.gmail.com>

On 09/02/10 13:08, Lucas De Marchi wrote:
> On Thu, Sep 2, 2010 at 17:00, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> It looks good for Documentation/.
>>
>> And fixing typos is certainly something that we want to do in
>> user-visible messages, like printk strings.
> 
> What about comments and code?


That will require a lot more detailed review IMO.
Usually it is good to have, but not nearly as important as user-visible strings.

And you should copy trivial@kernel.org on the patch.

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-09-02 20:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 19:05 [RFC] Fix typos Lucas De Marchi
2010-09-02 19:18 ` Randy Dunlap
2010-09-02 19:31   ` Lucas De Marchi
2010-09-02 20:00     ` Randy Dunlap
2010-09-02 20:08       ` Lucas De Marchi
2010-09-02 20:13         ` Randy Dunlap [this message]
2010-09-02 20:47           ` Lucas De Marchi
2010-09-02 20:16         ` Mike Frysinger
2010-09-02 20:23           ` Lucas De Marchi
2010-09-02 20:25       ` Randy Dunlap
2010-09-02 20:45         ` Lucas De Marchi
2010-09-03  2:29     ` Phillip Lougher
2010-09-03  2:45       ` Lucas De Marchi
2010-09-03  5:20         ` Lucas De Marchi
2010-09-03  5:23           ` Lucas De Marchi
2010-09-02 19:32   ` Mike Frysinger
2010-09-03  2:17   ` Phillip Lougher
2010-09-07 16:06   ` Paul E. McKenney
2010-09-07 16:47   ` Len Brown
2010-09-07 17:01     ` Lucas De Marchi
2010-09-07 17:30   ` Jason Wessel

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=4C800559.10701@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    /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