All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Rafał Miłecki" <zajec5@gmail.com>
Subject: Re: linux-next: build failure after merge of the wireless-drivers-next tree
Date: Mon, 27 Jul 2015 08:41:49 +0300	[thread overview]
Message-ID: <876156b1ia.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20150722103239.04995fda@canb.auug.org.au> (Stephen Rothwell's message of "Wed, 22 Jul 2015 10:32:39 +1000")

Hi Stephen,

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> After merging the wireless-drivers-next tree, today's linux-next build
> (x86_64 allmodconfig) failed like this:
>
> ERROR: "of_default_bus_match_table" [drivers/bcma/bcma.ko] undefined!
>
> Caused by commit
>
>   cae761b5a6bd ("bcma: populate bus DT subnodes as platform_device-s")
>
> I have used the wireless-drivers-next tree from next-20150721 for today.

Yesterday I pushed the commit below which should fix this issue. Please
let me know if you still have any problems.

commit 92ff7a698badec3938edd3ba6b3e3ae035555365
Author: Hauke Mehrtens <hauke@hauke-m.de>
Date:   Sat Jul 25 21:10:27 2015 +0200

    bcma: fix build error when build as module
    
    Currently of_default_bus_match_table is not exported so we can only use
    this feature when bcma is build into the kernel. This patch removes
    support for child buses when bcma is build as a module as a temporary
    fix for a build problem introduces in this commit:
    
    commit cae761b5a6bdc597ba476a040fdcd5b4bc559b85
    Author: Rafal Milecki <zajec5@gmail.com>
    Date:   Sun Jun 28 17:17:13 2015 +0200
    
        bcma: populate bus DT subnodes as platform_device-s
    
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Fixes: cae761b5a6bd ("bcma: populate bus DT subnodes as platform_device-s")
    Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
    Signed-off-by: Kalle Valo <kvalo@codeaurora.org>


-- 
Kalle Valo

  parent reply	other threads:[~2015-07-27  5:41 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22  0:32 linux-next: build failure after merge of the wireless-drivers-next tree Stephen Rothwell
2015-07-22  6:07 ` Kalle Valo
2015-07-27  5:41 ` Kalle Valo [this message]
2015-07-27  6:04   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2020-12-08  8:49 Stephen Rothwell
2020-12-08  8:54 ` Kalle Valo
2018-08-03  8:29 Stephen Rothwell
2018-08-03  9:09 ` Kalle Valo
2018-08-03  9:11 ` Stanislaw Gruszka
2018-08-03  9:21   ` Stanislaw Gruszka
2017-06-08  2:27 Stephen Rothwell
2017-06-08  2:43 ` Igor Mitsyanko
2017-06-08  2:57   ` Stephen Rothwell
2017-06-08 12:07     ` Kalle Valo
2017-06-08 12:47       ` Stephen Rothwell
2017-06-13  2:00 ` Stephen Rothwell
2017-06-15 16:08   ` David Miller
2017-06-15 18:25     ` Stephen Rothwell
2016-07-19  6:08 Stephen Rothwell
2016-07-19  6:08 ` Stephen Rothwell
2016-07-19  6:30 ` Kalle Valo
2016-07-19  6:51   ` Rafał Miłecki
2016-07-19  7:09     ` Kalle Valo
2016-07-19  7:09       ` Kalle Valo
     [not found]       ` <871t2qw1cz.fsf-HodKDYzPHsUD5k0oWYwrnHL1okKdlPRT@public.gmane.org>
2016-07-19  7:11         ` Rafał Miłecki
2016-07-19  7:11           ` Rafał Miłecki
2016-07-19 14:08           ` Kalle Valo
2016-07-19 14:08             ` Kalle Valo
2016-07-19 18:39             ` Brian Norris
2016-07-19 23:36               ` Stephen Rothwell
2016-07-20 18:31               ` Kalle Valo
2016-02-18 23:10 Stephen Rothwell
2016-02-19  8:08 ` Kalle Valo
2015-08-07  3:16 Stephen Rothwell
2015-08-09  8:41 ` Kalle Valo
2015-05-27  2:03 Stephen Rothwell
2015-05-27  9:08 ` Arend van Spriel
2015-05-27  9:08   ` Arend van Spriel
2015-05-28  1:38   ` Stephen Rothwell
2015-05-28  1:38     ` Stephen Rothwell
2015-01-27  8:03 Stephen Rothwell
2015-01-27  8:13 ` Kalle Valo

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=876156b1ia.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.