From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Mike Frysinger" <vapier.adi@gmail.com>
Cc: "Bryan Wu" <cooloney@kernel.org>, "Julia Lawall" <julia@diku.dk>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blackfin/sram: use 'unsigned long' for irqflags
Date: Wed, 6 Aug 2008 13:28:22 +0200 [thread overview]
Message-ID: <19f34abd0808060428m1c317531v4a58679c4051c0e9@mail.gmail.com> (raw)
In-Reply-To: <8bd0f97a0808060405qf70ead2t2f2604802875197e@mail.gmail.com>
Hi,
On Wed, Aug 6, 2008 at 1:05 PM, Mike Frysinger <vapier.adi@gmail.com> wrote:
> On Wed, Aug 6, 2008 at 6:58 AM, Vegard Nossum wrote:
>> From 3ef36948a88a968eec1b09859aa251dc6727df4e Mon Sep 17 00:00:00 2001
>> From: Vegard Nossum <vegard.nossum@gmail.com>
>> Date: Wed, 6 Aug 2008 12:00:23 +0200
>> Subject: [PATCH] blackfin/sram: use 'unsigned long' for irqflags
>>
>> Using just 'unsigned' will make flags an unsigned int. While this is
>> arguably not an error on blackfin where sizeof(int) == sizeof(long),
>> the patch is still justified on the grounds of principle.
>
> indeed, thanks
>
>> The patch was generated using the Coccinelle semantic patch framework.
>
> spam ?
Hm? I'm sorry, I don't understand what you mean by that. Do you think
the credit is undeserved?
>
>> Cc: Julia Lawall <julia@diku.dk>
>> Cc: Alexey Dobriyan <adobriyan@gmail.com>
>> Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com>
>
> should be CC Bryan Wu as well ...
> -mike
>
Oh right. I believed that Bryan Wu is the maintainer who would
eventually apply the patch, therefore I put him as a direct recipient
of the e-mail (To-field) and that he would add his Signed-off-by line
which would make the Cc-line redundant. I guess it makes some sense to
also list the maintainer in the patch Ccs since the patch itself may
be separate from the raw e-mail (e.g. in mail archives, which
generally don't display To: or Cc: fields). I didn't realize this
before.
Thanks.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-08-06 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 10:58 Vegard Nossum
2008-08-06 11:05 ` Mike Frysinger
2008-08-06 11:28 ` Vegard Nossum [this message]
2008-08-06 12:14 ` Mike Frysinger
2008-08-06 12:17 ` Mike Frysinger
2008-08-06 12:21 ` Julia Lawall
2008-08-06 12:52 ` Vegard Nossum
2008-08-06 17:34 ` Mike Frysinger
2008-08-22 13:44 ` Mike Frysinger
2008-08-27 6:56 ` Bryan Wu
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=19f34abd0808060428m1c317531v4a58679c4051c0e9@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=adobriyan@gmail.com \
--cc=cooloney@kernel.org \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@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
all inboxes | Powered by JetHome®