From: linux@prisktech.co.nz (Tony Prisk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] irqchip: vt8500: Move irq code to drivers/irqchip
Date: Thu, 03 Jan 2013 17:53:57 +1300 [thread overview]
Message-ID: <1357188837.9052.5.camel@gitbox> (raw)
In-Reply-To: <50E50B45.4040501@gmail.com>
On Wed, 2013-01-02 at 22:38 -0600, Rob Herring wrote:
> > CC: Thomas Gleixner <tglx@linutronix.de>
> > arch/arm/mach-vt8500/Makefile | 2 +-
> > arch/arm/mach-vt8500/common.h | 7 +-
> > arch/arm/mach-vt8500/irq.c | 253 -----------------------------------------
> > drivers/irqchip/Makefile | 1 +
> > drivers/irqchip/irq-vt8500.c | 253 +++++++++++++++++++++++++++++++++++++++++
>
> It's easy to forget, but please post using the -M option so only real
> changes are shown.
Ok.
> > -/* defined in irq.c */
> > +/* defined in drivers/irqchip/irq.c */
> > +int __init vt8500_irq_init(struct device_node *node,
> > + struct device_node *parent);
> > asmlinkage void vt8500_handle_irq(struct pt_regs *regs);
>
> These should go away with irqchip infrastructure Thomas and I have been
> working on. I plan to post updated version in the next day.
>
> Rob
Do you want me to rebase this patch on the new infrastructure once it's
in a tree somewhere, or was this a heads-up that it will need another
patch at some point?
I only ask because if these patches need to be separated it will created
merge-conflicts with arm-soc later on.
Regards
Tony P
WARNING: multiple messages have this Message-ID (diff)
From: Tony Prisk <linux@prisktech.co.nz>
To: Rob Herring <robherring2@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
vt8500-wm8505-linux-kernel@googlegroups.com,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Subject: Re: [PATCH 2/2] irqchip: vt8500: Move irq code to drivers/irqchip
Date: Thu, 03 Jan 2013 17:53:57 +1300 [thread overview]
Message-ID: <1357188837.9052.5.camel@gitbox> (raw)
In-Reply-To: <50E50B45.4040501@gmail.com>
On Wed, 2013-01-02 at 22:38 -0600, Rob Herring wrote:
> > CC: Thomas Gleixner <tglx@linutronix.de>
> > arch/arm/mach-vt8500/Makefile | 2 +-
> > arch/arm/mach-vt8500/common.h | 7 +-
> > arch/arm/mach-vt8500/irq.c | 253 -----------------------------------------
> > drivers/irqchip/Makefile | 1 +
> > drivers/irqchip/irq-vt8500.c | 253 +++++++++++++++++++++++++++++++++++++++++
>
> It's easy to forget, but please post using the -M option so only real
> changes are shown.
Ok.
> > -/* defined in irq.c */
> > +/* defined in drivers/irqchip/irq.c */
> > +int __init vt8500_irq_init(struct device_node *node,
> > + struct device_node *parent);
> > asmlinkage void vt8500_handle_irq(struct pt_regs *regs);
>
> These should go away with irqchip infrastructure Thomas and I have been
> working on. I plan to post updated version in the next day.
>
> Rob
Do you want me to rebase this patch on the new infrastructure once it's
in a tree somewhere, or was this a heads-up that it will need another
patch at some point?
I only ask because if these patches need to be separated it will created
merge-conflicts with arm-soc later on.
Regards
Tony P
next prev parent reply other threads:[~2013-01-03 4:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 3:25 [PATCH 0/2] Move some mach-vt8500 functions to new directories Tony Prisk
2013-01-03 3:25 ` Tony Prisk
2013-01-03 3:25 ` [PATCH 1/2] timer: vt8500: Move system timer to clocksource Tony Prisk
2013-01-03 3:25 ` Tony Prisk
2013-01-03 7:35 ` Dmitry Torokhov
2013-01-03 7:35 ` Dmitry Torokhov
2013-01-03 7:45 ` Joe Perches
2013-01-03 7:45 ` Joe Perches
2013-01-03 8:07 ` Arnd Bergmann
2013-01-03 8:07 ` Arnd Bergmann
2013-01-03 17:29 ` Stephen Warren
2013-01-03 17:29 ` Stephen Warren
2013-01-03 3:25 ` [PATCH 2/2] irqchip: vt8500: Move irq code to drivers/irqchip Tony Prisk
2013-01-03 3:25 ` Tony Prisk
2013-01-03 4:38 ` Rob Herring
2013-01-03 4:38 ` Rob Herring
2013-01-03 4:53 ` Tony Prisk [this message]
2013-01-03 4:53 ` Tony Prisk
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=1357188837.9052.5.camel@gitbox \
--to=linux@prisktech.co.nz \
--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.