From: Stephen Boyd <sboyd@codeaurora.org>
To: Vinayak Kale <vkale@apm.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>, tglx <tglx@linutronix.de>,
Will Deacon <will.deacon@arm.com>,
"jcm@redhat.com" <jcm@redhat.com>
Subject: Re: [PATCH V4 1/2] genirq: Add an accessor for IRQ_PER_CPU flag
Date: Thu, 21 Nov 2013 16:54:12 -0800 [thread overview]
Message-ID: <528EAB34.6010105@codeaurora.org> (raw)
In-Reply-To: <CAPrCYkdpHPPY6D1dj5R=QJ5mtmKUfTx+M7wRMV-t2LrZMdSW9w@mail.gmail.com>
On 11/20/13 22:10, Vinayak Kale wrote:
> [removing chris.smith@st.com]
>
> On Thu, Nov 21, 2013 at 11:36 AM, Vinayak Kale <vkale@apm.com> wrote:
>> On Wed, Nov 20, 2013 at 11:46 PM, Stephen Boyd <sboyd@codeaurora.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@apm.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@st.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
next prev parent reply other threads:[~2013-11-22 0:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 11:13 [PATCH V4 0/2] genirq: arm64: perf: support for percpu pmu interrupt Vinayak Kale
2013-11-20 11:13 ` [PATCH V4 1/2] genirq: Add an accessor for IRQ_PER_CPU flag Vinayak Kale
2013-11-20 18:16 ` Stephen Boyd
2013-11-21 6:06 ` Vinayak Kale
2013-11-21 6:10 ` Vinayak Kale
2013-11-22 0:54 ` Stephen Boyd [this message]
2013-11-22 6:45 ` Vinayak Kale
2013-11-20 11:13 ` [PATCH V4 2/2] arm64: perf: add support for percpu pmu interrupt Vinayak Kale
2013-11-20 13:14 ` Marc Zyngier
2013-11-20 17:28 ` Vinayak Kale
2013-11-20 18:00 ` Will Deacon
2013-11-21 6:22 ` Vinayak Kale
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=528EAB34.6010105@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vkale@apm.com \
--cc=will.deacon@arm.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