From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] arm: Move chained_irq_(enter|exit) to a generic file
Date: Fri, 25 Jan 2013 12:30:40 +0530 [thread overview]
Message-ID: <51022D98.2060205@ti.com> (raw)
In-Reply-To: <20130124172919.GI18233@arm.com>
On Thursday 24 January 2013 10:59 PM, Catalin Marinas wrote:
> On Thu, Jan 24, 2013 at 05:32:09AM +0000, Santosh Shilimkar wrote:
>> On Wednesday 23 January 2013 11:29 PM, Catalin Marinas wrote:
>>> diff --git a/include/linux/irqchip/chained_irq.h b/include/linux/irqchip/chained_irq.h
>>> new file mode 100644
>>> index 0000000..adf4c30
>>> --- /dev/null
>>> +++ b/include/linux/irqchip/chained_irq.h
>>> @@ -0,0 +1,52 @@
>>> +/*
>>> + * Chained IRQ handlers support.
>>> + *
>>> + * Copyright (C) 2011 ARM Ltd.
>>
>> 2013 now ;)
>
> I thought about this but decided to keep the year when the chained IRQ
> functions were contributed by Will (still ARM's copyright).
>
Ahh. Its just move to the new file. As you prefer but 2011-13 will
do as well :-)
next prev parent reply other threads:[~2013-01-25 7:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:59 [PATCH 0/4] Preparatory GIC patches for arm64 support Catalin Marinas
2013-01-23 17:59 ` [PATCH 1/4] arm: Move the set_handle_irq and handle_arch_irq declarations to asm/irq.h Catalin Marinas
2013-01-23 17:59 ` [PATCH 2/4] arm: Move chained_irq_(enter|exit) to a generic file Catalin Marinas
2013-01-24 5:32 ` Santosh Shilimkar
2013-01-24 17:29 ` Catalin Marinas
2013-01-25 7:00 ` Santosh Shilimkar [this message]
2013-01-23 17:59 ` [PATCH 3/4] irqchip: gic: Call handle_bad_irq() directly Catalin Marinas
2013-01-23 17:59 ` [PATCH 4/4] irqchip: gic: Perform the gic_secondary_init() call via CPU notifier Catalin Marinas
2013-01-23 18:28 ` Stephen Warren
2013-01-24 2:15 ` Viresh Kumar
2013-01-24 5:33 ` Santosh Shilimkar
2013-01-24 17:51 ` Rob Herring
2013-01-25 4:30 ` Simon Horman
2013-01-25 9:25 ` Catalin Marinas
2013-01-28 1:03 ` Simon Horman
2013-01-25 11:25 ` Srinidhi Kasagar
2013-01-25 16:16 ` Dinh Nguyen
2013-01-25 18:12 ` Catalin Marinas
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=51022D98.2060205@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.