From: Rob Herring <robh@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Simon Horman <horms@verge.net.au>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Russell King <linux@arm.linux.org.uk>,
Jason Cooper <jason@lakedaemon.net>,
Alexander Shiyan <shc_work@mail.ru>,
Stephen Warren <swarren@wwwdotorg.org>,
David Airlie <airlied@linux.ie>,
Catalin Marinas <catalin.marinas@arm.com>,
Lee Jones <lee@kernel.org>, Will Deacon <will.deacon@arm.com>,
dri-devel@lists.freedesktop.org, Kukjin Kim <kgene@kernel.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 RESEND 0/5] Remaining part of kill off set_irq_flags usage
Date: Wed, 16 Sep 2015 09:12:13 -0500 [thread overview]
Message-ID: <55F978BD.3030203@kernel.org> (raw)
In-Reply-To: <1440889285-5637-1-git-send-email-robh@kernel.org>
On 08/29/2015 06:01 PM, Rob Herring wrote:
> Thomas,
>
> As requested, here are the remaining patches for killing off
> set_irq_flags which have not been picked up. The rest of the
> series has been picked up and are in -next.
Thomas, are you going to pick up these remaining patches?
Rob
>
> Rob
>
> Rob Herring (5):
> gpu/drm: kill off set_irq_flags usage
> irqchip: kill off set_irq_flags usage
> sh: kill off set_irq_flags usage
> ARM: remove ununsed set_irq_flags
> arm64: remove ununsed set_irq_flags
>
> arch/arm/include/asm/hw_irq.h | 6 ------
> arch/arm/kernel/irq.c | 20 --------------------
> arch/arm64/include/asm/hardirq.h | 5 -----
> drivers/gpu/drm/msm/mdp/mdp5/mdp5_irq.c | 1 -
> drivers/gpu/ipu-v3/ipu-common.c | 3 +--
> drivers/irqchip/exynos-combiner.c | 2 +-
> drivers/irqchip/irq-armada-370-xp.c | 3 +--
> drivers/irqchip/irq-bcm2835.c | 2 +-
> drivers/irqchip/irq-clps711x.c | 6 +++---
> drivers/irqchip/irq-gic-v3.c | 5 ++---
> drivers/irqchip/irq-gic.c | 4 ++--
> drivers/irqchip/irq-hip04.c | 4 ++--
> drivers/irqchip/irq-keystone.c | 2 +-
> drivers/irqchip/irq-mmp.c | 3 ---
> drivers/irqchip/irq-mxs.c | 1 -
> drivers/irqchip/irq-renesas-intc-irqpin.c | 1 -
> drivers/irqchip/irq-renesas-irqc.c | 1 -
> drivers/irqchip/irq-s3c24xx.c | 14 ++------------
> drivers/irqchip/irq-sun4i.c | 2 +-
> drivers/irqchip/irq-versatile-fpga.c | 2 +-
> drivers/irqchip/irq-vic.c | 2 +-
> drivers/irqchip/irq-vt8500.c | 1 -
> drivers/irqchip/spear-shirq.c | 1 -
> drivers/sh/intc/internals.h | 10 +---------
> 24 files changed, 20 insertions(+), 81 deletions(-)
>
next prev parent reply other threads:[~2015-09-16 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 23:01 [PATCH v3 RESEND 0/5] Remaining part of kill off set_irq_flags usage Rob Herring
2015-08-29 23:01 ` [RESEND PATCH v3 1/5] gpu/drm: " Rob Herring
2015-08-31 14:13 ` [PATCH v3 RESEND 0/5] Remaining part of " Thomas Gleixner
2015-09-16 14:12 ` Rob Herring [this message]
2015-09-16 14:15 ` Thomas Gleixner
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=55F978BD.3030203@kernel.org \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=catalin.marinas@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=maxime.ripard@free-electrons.com \
--cc=shc_work@mail.ru \
--cc=swarren@wwwdotorg.org \
--cc=tglx@linutronix.de \
--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