All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	"Arnd Bergmann" <arnd@arndb.de>
Subject: Re: [PATCH] bcma: Add dependency on OF_ADDRESS
Date: Thu, 9 Oct 2014 19:18:31 +0200	[thread overview]
Message-ID: <5436C367.5080908@broadcom.com> (raw)
In-Reply-To: <5436C2B4.6030801@broadcom.com>

On 10/09/14 19:15, Arend van Spriel wrote:
> On 10/09/14 18:54, Rafał Miłecki wrote:
>> On 9 October 2014 18:41, Guenter Roeck<linux@roeck-us.net> wrote:
>>> Commit 2101e533f41a ("bcma: register bcma as device tree driver")
>>> introduces a hard dependency on OF_ADDRESS into the bcma driver.
>>> OF_ADDRESS is specifically disabled for the sparc architecture.
>>> This results in the following error when building sparc64:allmodconfig.
>
> Does this mean on sparc (using allmodconfig) you will get CONFIG_OF and
> !CONFIG_OF_ADDRESS? Does that makes sense?

Is CONFIG_OF is used on sparc to access OpenBoot information?

Regards,
Arend

> btw. the OF_ADDRESS dependency was introduced by commit "bcma: get IRQ
> numbers from dt".
>
> Regards,
> Arend
>
>> Won't this make bcma im-POSSIBLE on MIPS? And maybe x86(_64), or at
>> least add an unneeded dependency? I think we should somehow limit this
>> to BCM5301X arch.
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/


  reply	other threads:[~2014-10-09 17:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 16:41 [PATCH] bcma: Add dependency on OF_ADDRESS Guenter Roeck
2014-10-09 16:54 ` Rafał Miłecki
2014-10-09 17:15   ` Guenter Roeck
2014-10-09 17:15   ` Arend van Spriel
2014-10-09 17:18     ` Arend van Spriel [this message]
2014-10-09 17:29       ` Guenter Roeck
2014-10-09 18:28         ` Hauke Mehrtens
2014-10-09 19:25           ` Guenter Roeck
2014-10-09 21:48             ` Hauke Mehrtens
2014-10-09 21:57               ` Guenter Roeck
2014-10-10  9:30               ` Arend van Spriel
2014-10-09 21:39           ` [PATCH] bcma: fix build when CONFIG_OF_ADDRESS is not set Hauke Mehrtens
2014-10-09 21:46             ` Guenter Roeck
2014-10-25 20:36             ` Guenter Roeck
2014-10-27 15:15               ` John W. Linville
2014-10-27 15:42                 ` Guenter Roeck
2014-10-09 17:21     ` [PATCH] bcma: Add dependency on OF_ADDRESS Guenter Roeck
2014-10-10  0:24       ` Julian Calaby
2014-10-10  0:24         ` Julian Calaby
2014-10-10  4:32         ` David Miller
2014-10-10  4:32           ` David Miller
2014-10-09 17:28     ` Guenter Roeck

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=5436C367.5080908@broadcom.com \
    --to=arend@broadcom.com \
    --cc=arnd@arndb.de \
    --cc=hauke@hauke-m.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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.