mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Andy Whitcroft" <apw@shadowen.org>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Change a WARN message in checkpatch
Date: Mon, 28 Jan 2008 16:13:34 +0100	[thread overview]
Message-ID: <4d8e3fd30801280713n7139223fj91adca85c76b60ad@mail.gmail.com> (raw)
In-Reply-To: <20080128145605.GI12910@shadowen.org>

On Jan 28, 2008 3:56 PM, Andy Whitcroft <apw@shadowen.org> wrote:
> On Mon, Jan 14, 2008 at 11:29:13PM +0100, Paolo Ciarrocchi wrote:
> > Hi Andy,
> > When I started using checkpatch I was confused by the following WARN message:
> >
> >       no space between function name and open parenthesis
> >
> > I thought the problem was that a space was missing while the truth is the opposite.
> >
> > How about the following patch?
>
> I can see how that language would be confusing.  Your patch makes the
> english clearer, but somehow seems clumsy.  There must be a better way
> to say this.  I will think on it and see what I can come up with.

Fair enought, I'm not English mother tongue and I'm sure you can come
up with a better
sentence :-)

BTW, is there a public repo I can track to look at all the new patches?

Thanks.

Ciao,
-- 
Paolo
http://paolo.ciarrocchi.googlepages.com/

  reply	other threads:[~2008-01-28 15:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 22:29 Paolo Ciarrocchi
2008-01-28 14:56 ` Andy Whitcroft
2008-01-28 15:13   ` Paolo Ciarrocchi [this message]
2008-02-23 13:38     ` Paolo Ciarrocchi
2008-02-24 15:18       ` Benny Halevy
2008-02-24 18:14         ` Paolo Ciarrocchi
2008-02-25  3:29           ` Andy Whitcroft
2008-02-25  5:47             ` Benny Halevy
2008-02-25  6:51             ` Paolo Ciarrocchi
2008-02-25 10:53               ` Andy Whitcroft
  -- strict thread matches above, loose matches on Subject: below --
2008-01-04 12:45 Paolo Ciarrocchi

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=4d8e3fd30801280713n7139223fj91adca85c76b60ad@mail.gmail.com \
    --to=paolo.ciarrocchi@gmail.com \
    --cc=apw@shadowen.org \
    --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
all inboxes | Powered by JetHome®