mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hauke Mehrtens <hauke@hauke-m.de>,
	John Crispin <blogic@openwrt.org>
Subject: linux-next: build failure after merge of the mips tree
Date: Mon, 18 Feb 2013 10:43:40 +1100	[thread overview]
Message-ID: <20130218104340.eb5e20da05dffe89ac4da693@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

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.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-02-17 23:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-17 23:43 Stephen Rothwell [this message]
2013-02-17 23:59 ` Hauke Mehrtens
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=20130218104340.eb5e20da05dffe89ac4da693@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=blogic@openwrt.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ralf@linux-mips.org \
    /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®