From: zhangfei <zhangfei.gao@linaro•org>
To: Robin Gong <yibin.gong@nxp•com>,
Stephen Rothwell <sfr@canb•auug.org.au>,
Vinod Koul <vkoul@kernel•org>, John Garry <john.garry@huawei•com>,
Arnd Bergmann <arnd@arndb•de>, Rob Herring <robh@kernel•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Angelo Dureghello <angelo@sysam•it>
Subject: Re: linux-next: build failure after merge of the slave-dma tree
Date: Mon, 8 Jul 2019 11:06:29 +0800 [thread overview]
Message-ID: <58c9b815-9bfc-449c-6017-c6da582dffc5@linaro.org> (raw)
In-Reply-To: <VE1PR04MB6638080C43EC68EFF9F7B38A89F60@VE1PR04MB6638.eurprd04.prod.outlook.com>
Hi, Robin
On 2019/7/8 上午9:22, Robin Gong wrote:
> Hi Stephen,
> That's caused by 'of_irq_count' NOT export to global symbol, and I'm curious why it has been
> here for so long since Zhangfei found it in 2015. https://patchwork.kernel.org/patch/7404681/
> Hi Rob,
> Is there something I miss so that Zhangfei's patch not accepted finally?
>
>
I remembered Rob suggested us not using of_irq_count and use
platform_get_irq etc.
https://lkml.org/lkml/2015/11/18/466
So we remove of_irq_count
commit 8c77dca011125b795bfa1c86f85a80132feee578
Author: John Garry <john.garry@huawei•com>
Date: Thu Nov 19 20:23:59 2015 +0800
hisi_sas: Remove dependency on of_irq_count
Thanks
next prev parent reply other threads:[~2019-07-08 3:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 7:31 linux-next: build failure after merge of the slave-dma tree Stephen Rothwell
2019-07-06 13:43 ` Robin Gong
2019-07-06 14:43 ` Vinod Koul
2019-07-08 2:01 ` Robin Gong
2019-07-08 4:09 ` Vinod Koul
2019-07-08 1:22 ` Robin Gong
2019-07-08 3:06 ` zhangfei [this message]
2019-07-08 4:17 ` Vinod Koul
2019-07-08 4:54 ` Robin Gong
2019-07-08 4:48 ` Robin Gong
-- strict thread matches above, loose matches on Subject: below --
2018-10-04 5:44 Stephen Rothwell
2018-10-04 6:13 ` Vinod
2017-08-22 5:36 Stephen Rothwell
2017-08-22 16:39 ` Vinod Koul
2016-09-16 3:18 Stephen Rothwell
2016-09-16 8:34 ` Peter Griffin
2016-09-19 16:38 ` Vinod Koul
2015-10-15 0:51 Stephen Rothwell
2015-10-15 3:35 ` Koul, Vinod
2015-10-15 3:51 ` Stephen Rothwell
2015-10-15 14:07 ` Arnd Bergmann
2015-10-15 14:27 ` Stephen Rothwell
2015-08-06 2:22 Stephen Rothwell
2015-08-06 3:00 ` Vinod Koul
2015-08-24 6:53 ` Maxime Ripard
2015-08-24 8:11 ` Vinod Koul
2015-08-24 9:21 ` Maxime Ripard
2015-02-16 1:09 Stephen Rothwell
2015-02-16 1:48 ` Yibin Gong
2015-02-16 4:06 ` Vinod Koul
2014-12-09 3:48 Stephen Rothwell
2014-12-09 4:47 ` Vinod Koul
2014-11-10 0:58 Stephen Rothwell
2014-11-10 5:06 ` Vinod Koul
2014-11-12 13:23 ` Ludovic Desroches
2014-09-12 3:17 Stephen Rothwell
2014-09-15 9:51 ` Geert Uytterhoeven
2014-07-28 2:18 Stephen Rothwell
2014-07-28 7:16 ` Vinod Koul
2014-07-28 11:56 ` Maxime Ripard
2013-04-02 1:57 Stephen Rothwell
2013-04-02 1:38 ` Vinod Koul
2013-01-07 0:26 Stephen Rothwell
2013-01-07 14:00 ` Vinod Koul
2012-06-22 3:00 Stephen Rothwell
2012-06-22 5:01 ` Vinod Koul
2012-06-25 1:21 ` Zhangfei Gao
2012-03-27 0:52 Stephen Rothwell
2012-03-27 8:33 ` Vinod Koul
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=58c9b815-9bfc-449c-6017-c6da582dffc5@linaro.org \
--to=zhangfei.gao@linaro$(echo .)org \
--cc=angelo@sysam$(echo .)it \
--cc=arnd@arndb$(echo .)de \
--cc=john.garry@huawei$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=robh@kernel$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=vkoul@kernel$(echo .)org \
--cc=yibin.gong@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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