linux-kernel - Re: [PATCH V4 1/2] genirq: Add an accessor for IRQ_PER

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <528EAB34.6010105@codeaurora.org>
Date:	Thu, 21 Nov 2013 16:54:12 -0800
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Vinayak Kale <vkale@....com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>, tglx <tglx@...utronix.de>,
	Will Deacon <will.deacon@....com>,
	"jcm@...hat.com" <jcm@...hat.com>
Subject: Re: [PATCH V4 1/2] genirq: Add an accessor for IRQ_PER_CPU flag

On 11/20/13 22:10, Vinayak Kale wrote:
> [removing chris.smith@...com]
>
> On Thu, Nov 21, 2013 at 11:36 AM, Vinayak Kale <vkale@....com> wrote:
>> On Wed, Nov 20, 2013 at 11:46 PM, Stephen Boyd <sboyd@...eaurora.org> wrote:
>>> On 11/20/13 03:13, Vinayak Kale wrote:
>>>> This patch adds an accessor function for IRQ_PER_CPU flag.
>>>> The accessor function is useful to dertermine whether an IRQ is percpu or not.
>>>>
>>>> Signed-off-by: Vinayak Kale <vkale@....com>
>>>> ---
>>> This looks like a copy of Chris Smith's patch. Shouldn't Chris be the
>>> author and the commit text be whatever Chris sent?
>> In the cover letter of this patch series I did mention about Chris's
>> earlier patch. I didn't know his email-id earlier, have found the
>> mail-id now. CCing the mail-id to check whether it's still valid.
>>
> Chris's mail-id doesn't seem to be valid, the earlier mail to his
> mail-id [chris.smith@...com] bounced.
> Please let me know in such case how to mention original author's credits.

It's up to the maintainer accepting the patch. If I was picking up the
patch I would say it doesn't really matter if the mail-id is valid
anymore. Leave the original patch intact and just add your sign-off. If
you took the patch and significantly changed it it's good to put
"Based-on-a-patch-by:" and then take over authorship.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/