From: Hauke Mehrtens <hauke@hauke-m•de>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Ralf Baechle <ralf@linux-mips•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
John Crispin <blogic@openwrt•org>
Subject: Re: linux-next: build failure after merge of the mips tree
Date: Mon, 18 Feb 2013 00:59:20 +0100 [thread overview]
Message-ID: <51216ED8.5040906@hauke-m.de> (raw)
In-Reply-To: <20130218104340.eb5e20da05dffe89ac4da693@canb.auug.org.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/18/2013 12:43 AM, Stephen Rothwell wrote:
> Hi Ralf,
>
> After merging the mips tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/ssb/driver_gpio.c: In function 'ssb_gpio_chipco_to_irq':
> drivers/ssb/driver_gpio.c:82:3: error: implicit declaration of
> function 'ssb_mips_irq' [-Werror=implicit-function-declaration]
>
> Caused by commit d630dd4ef20f ("ssb: add gpio_to_irq again").
>
> I have used the mips tree from next-20130215 for today.
>
Hi Ralf and blogic,
Could you drop this patch [0] and this one [1].
I saw that they are not any more in blogic tree.
Hauke
[0]: https://patchwork.linux-mips.org/patch/4719/
[1]: https://patchwork.linux-mips.org/patch/4720/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBAgAGBQJRIW7SAAoJEIZ0px9YPRMySfMQAII6ZFgh+dDS/gEhxCmZ5EJZ
dmz5AjafHmmqAKuw5j5erKvRzocxaxwLscvEjv6WXD/dGD7DoUkixSkoHD0G5ptE
gba3OL8qqBQGzuqhUsfKCnYS3b7UGYC95G9qS03jcikm46Rl3ufpEnOswkIwyssw
Qd0yVqvsmXDaTz6LljwSYGT6BxLo63QmoaxH64yCXwYtOh+vGanif8U+QZcg61Hm
jL1CRlbzjJg5VrtTOak9SVsRFRp4TOvJe7TI5P/Nm20mkt6q+1sWcoOXa1egG0k7
68Y2hTzlERTK6LCpmHRZcQxXPbMl/KP03+mgtqcN5xQtkGq4NfcnfG0HIANo9fpf
BlnCX//gDaLRVcwlQnAShVYRcLd+tjb6l+2ObYLShJVFPdD5YJ3sTiySKW7xVW04
iFlzxDWKYA2NILHldHHa+MX7r86IBPLrZhG+IqgdjLcw4zQZiGn2heVSQipzmPGm
eBWqJuSUtVYNrEFVd/+CcqHo5jvmqmybh7+DLi6fVBvNb1vh9ApmltVuD37T00CB
d3bOF5VEFQR+zoNloxriI84SCZPRu/in8f/Bqy9x+iGnkgW+FxnJnDi4kEaerNB7
jjZow64JwE5f/pYHle/ffLUvsCRLV7GpvJ33n4OxFQyVMYHrPEdbF2r+YkytA5zJ
KzZDEk6WfzVItcPcjSTg
=EwXd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-02-17 23:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 23:43 linux-next: build failure after merge of the mips tree Stephen Rothwell
2013-02-17 23:59 ` Hauke Mehrtens [this message]
2013-02-20 0:29 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2023-03-27 5:12 Stephen Rothwell
2023-03-27 8:41 ` Thomas Bogendoerfer
2020-04-20 10:07 Stephen Rothwell
2020-04-20 11:33 ` Thomas Bogendoerfer
2013-10-07 15:18 linux-next: Tree for Oct 7 Thierry Reding
2013-10-07 15:18 ` linux-next: build failure after merge of the mips tree Thierry Reding
2011-11-10 1:22 Stephen Rothwell
2010-07-27 1:14 Stephen Rothwell
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=51216ED8.5040906@hauke-m.de \
--to=hauke@hauke-m$(echo .)de \
--cc=blogic@openwrt$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ralf@linux-mips$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/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