From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: dougthompson@xmission.com, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: edac: struct device - replace bus_id with dev_name(), dev_set_name()
Date: Tue, 4 Nov 2008 00:05:35 +0100 [thread overview]
Message-ID: <ac3eb2510811031505s38c1519ck83f5d89c68566da8@mail.gmail.com> (raw)
In-Reply-To: <20081103145733.3b1701d1.akpm@linux-foundation.org>
On Mon, Nov 3, 2008 at 23:57, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Thu, 30 Oct 2008 01:39:05 +0100
> Kay Sievers <kay.sievers@vrfy.org> wrote:
>
>> Subject: edac: struct device - replace bus_id with dev_name(), dev_set_name()
>
> um,
>
> ERROR: space required after that ',' (ctx:VxV)
> #40: FILE: drivers/edac/edac_mc.c:404:
> + "%s (%s) %s %s already assigned %d\n",dev_name( p->dev),
> ^
>
> ERROR: space prohibited after that open parenthesis '('
> #40: FILE: drivers/edac/edac_mc.c:404:
> + "%s (%s) %s %s already assigned %d\n",dev_name( p->dev),
>
>
> where did this crap come from? It looks like some automated thing
> placed a space at the wrong end of the string?
>
> If so, are we about to send hundreds of such mistakes into the tree?
It was me feeling automated, maybe 4 am in the morning.
It's only one instance in the ~60 patches I have so far:
$ cat * | wc -l
7255
$ grep '( ' *
bus_id-edac.patch:+ "%s (%s) %s %s already assigned %d\n",dev_name( p->dev),
Sorry for that.
Thanks,
Kay
prev parent reply other threads:[~2008-11-03 23:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 0:39 Kay Sievers
2008-10-30 8:31 ` Doug Thompson
2008-11-03 22:57 ` Andrew Morton
2008-11-03 23:05 ` Kay Sievers [this message]
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=ac3eb2510811031505s38c1519ck83f5d89c68566da8@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=akpm@linux-foundation.org \
--cc=dougthompson@xmission.com \
--cc=greg@kroah.com \
--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®