From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the pinctrl tree
Date: Wed, 7 Dec 2016 15:22:32 +0100 [thread overview]
Message-ID: <CACRpkdZdFBrKyzGRBbWLm1UB-ehsnR_vMSrhLvJK9aH+dDF1bQ@mail.gmail.com> (raw)
In-Reply-To: <20161207083102.093fdf96@canb.auug.org.au>
On Tue, Dec 6, 2016 at 10:31 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Linus,
>
> On Mon, 5 Dec 2016 10:00:38 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the pinctrl tree, today's linux-next build (arm
>> multi_v7_defconfig) failed like this:
>>
>> drivers/gpio/gpio-pl061.c: In function 'pl061_irq_set_wake':
>> drivers/gpio/gpio-pl061.c:280:28: error: 'struct gpio_chip' has no member named 'irq_parent'
>> return irq_set_irq_wake(gc->irq_parent, state);
>> ^
>> drivers/gpio/gpio-pl061.c:281:1: warning: control reaches end of non-void function [-Wreturn-type]
>> }
>> ^
>>
>> Caused by commit
>>
>> d245b3f9bd36 ("gpio: simplify adding threaded interrupts")
>>
>> I have used the pinctrl tree from next-20161202 for today.
>
> I am still getting this.
Sorry. My intention was of course to put the required pl061 patches on
an immutable branch and pull into pinctrl as well.
Oh well.
FIxing it up now, sorry for the mess.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-12-07 14:22 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 23:00 linux-next: build failure after merge of the pinctrl tree Stephen Rothwell
2016-12-06 21:31 ` Stephen Rothwell
2016-12-07 14:22 ` Linus Walleij [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-28 2:23 Stephen Rothwell
2025-10-28 9:41 ` Linus Walleij
2025-07-14 7:08 Stephen Rothwell
2025-07-14 8:37 ` Luca Weiss
2025-07-14 15:54 ` Linus Walleij
2025-03-14 5:24 Stephen Rothwell
2025-03-14 11:03 ` Linus Walleij
2025-01-06 5:46 Stephen Rothwell
2025-01-08 21:47 ` Stephen Rothwell
2025-01-08 21:58 ` Linus Walleij
2025-01-09 11:27 ` Frank Wunderlich
2024-10-08 5:13 Stephen Rothwell
2024-10-09 16:02 ` Linus Walleij
2023-11-14 2:13 Stephen Rothwell
2023-11-14 7:46 ` Linus Walleij
2022-11-15 4:03 Stephen Rothwell
2022-11-10 4:09 Stephen Rothwell
2022-11-10 9:14 ` Linus Walleij
2022-11-09 2:46 Stephen Rothwell
2022-11-09 3:55 ` Yinbo Zhu
2022-11-09 8:31 ` Linus Walleij
2022-08-26 5:26 Stephen Rothwell
2022-08-26 8:01 ` Linus Walleij
2022-08-26 11:20 ` Wolfram Sang
2022-08-26 13:18 ` Linus Walleij
2022-09-12 13:40 ` Uwe Kleine-König
2022-08-02 22:21 broonie
2022-08-02 22:29 ` Mario Limonciello
2022-06-29 7:13 Stephen Rothwell
2022-06-27 6:01 Stephen Rothwell
2021-10-26 5:28 Stephen Rothwell
2021-10-26 12:30 ` Prathamesh Shete
2021-10-26 20:15 ` Linus Walleij
2021-10-26 21:21 ` Dmitry Osipenko
2021-10-28 12:31 ` Prathamesh Shete
2021-11-09 4:49 ` Linus Walleij
2021-03-04 1:12 Stephen Rothwell
2021-03-04 8:16 ` Linus Walleij
2021-03-04 9:54 ` Stephen Rothwell
[not found] ` <202103050813501649431@rock-chips.com>
2021-03-05 0:43 ` Linus Walleij
[not found] ` <202103050846457413391@rock-chips.com>
2021-03-05 2:12 ` Stephen Rothwell
2021-01-27 9:41 Stephen Rothwell
2021-01-27 12:40 ` Krzysztof Kozlowski
2020-10-30 1:50 Stephen Rothwell
2020-11-04 3:10 ` Stephen Rothwell
2020-11-04 14:02 ` Linus Walleij
2020-07-17 7:16 Stephen Rothwell
2020-07-17 9:01 ` Hanks Chen
2020-07-17 11:37 ` Linus Walleij
2020-03-30 6:19 Stephen Rothwell
2020-02-25 1:21 Stephen Rothwell
2020-02-25 9:14 ` Marco Felsch
2019-08-21 6:16 Stephen Rothwell
2019-08-21 7:00 ` Linus Walleij
2016-12-06 22:27 Peter Rosin
2016-12-06 22:46 ` Stephen Rothwell
2016-12-06 23:05 ` Peter Rosin
2016-05-12 4:14 Stephen Rothwell
2016-05-12 13:39 ` Linus Walleij
2015-12-21 4:58 Stephen Rothwell
2015-12-21 6:23 ` Pramod Kumar
2015-12-21 8:44 ` Linus Walleij
2015-12-18 3:45 Stephen Rothwell
2015-12-18 5:34 ` Pramod Kumar
2015-12-18 5:57 ` Stephen Rothwell
2015-12-18 6:12 ` Pramod Kumar
2015-12-18 17:05 ` Ray Jui
2015-09-25 3:34 Stephen Rothwell
2015-10-02 3:37 ` Stephen Rothwell
2015-10-05 7:38 ` Linus Walleij
2015-01-12 5:02 Stephen Rothwell
2015-01-12 7:25 ` Linus Walleij
2014-10-27 3:35 Stephen Rothwell
2014-05-30 6:08 Stephen Rothwell
2014-05-30 8:19 ` Linus Walleij
2014-02-11 3:56 Stephen Rothwell
2014-02-11 8:21 ` Linus Walleij
2013-12-10 3:02 Stephen Rothwell
2013-12-10 4:06 ` Stephen Rothwell
2013-12-10 8:50 ` Linus Walleij
2013-12-09 4:18 Stephen Rothwell
2013-09-20 3:27 Stephen Rothwell
2012-04-04 2:44 Stephen Rothwell
2012-04-04 3:43 ` Stephen Warren
2012-04-10 7:42 ` Linus Walleij
2012-04-10 15:12 ` Stephen Warren
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=CACRpkdZdFBrKyzGRBbWLm1UB-ehsnR_vMSrhLvJK9aH+dDF1bQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).