From: Thomas Gleixner <tglx@linutronix.de>
To: Ben Zhang <benzh@chromium.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Jason Cooper <jason@lakedaemon.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicolas Boichat <drinkcat@chromium.org>
Subject: Re: [PATCH] irqchip: gic-v3: Explicitly include linux/io.h
Date: Wed, 19 Aug 2015 23:13:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1508192313010.3873@nanos> (raw)
In-Reply-To: <CAOV7By+37xLq8=VeML=Gnf9FoQ7UVc_st9o+U-P9Pk3rfd956A@mail.gmail.com>
On Fri, 7 Aug 2015, Ben Zhang wrote:
> Mainline build is fine because commit 332fd7c4fef5("genirq: Generic
> chip: Change irq_reg_{readl,writel} arguments") landed before the
> timecounter patch, and it creates a new include path to the io.h
> header:
> arch/arm64/include/asm/io.h
> include/linux/io.h
> include/linux/irq.h
> include/linux/of_irq.h
> drivers/irqchip/irq-gic-v3.c
And why do we need to include it once more then?
Thanks,
tglx
next prev parent reply other threads:[~2015-08-19 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 5:31 Ben Zhang
2015-08-07 8:40 ` Marc Zyngier
2015-08-07 23:38 ` Ben Zhang
2015-08-19 21:13 ` Thomas Gleixner [this message]
2015-08-19 22:44 ` Ben Zhang
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=alpine.DEB.2.11.1508192313010.3873@nanos \
--to=tglx@linutronix.de \
--cc=benzh@chromium.org \
--cc=drinkcat@chromium.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@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
all inboxes | Powered by JetHome®