From: Ralf Baechle <ralf@linux-mips.org>
To: Manish Lachwani <mlachwani@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Fix Kconfig for Broadcom SWARM
Date: Fri, 4 Feb 2005 00:57:02 +0100 [thread overview]
Message-ID: <20050203235702.GA22311@linux-mips.org> (raw)
In-Reply-To: <4202611A.4000302@mvista.com>
On Thu, Feb 03, 2005 at 09:36:26AM -0800, Manish Lachwani wrote:
> The problem is that SIBYTE_SB1xxx_SOC is undefined. We need a small
> change in arch/mips/sibyte/Kconfig:
>
> config SIBYTE_SB1xxx_SOC
> bool "Support for Broadcom BCM1xxx SOCs "
>
> Since the ethernet driver, the serial driver and the CFE depend on this
> option to be selected else they wont be compiled in.
The fix for this is already in CVS since a few hours.
Ralf
prev parent reply other threads:[~2005-02-03 23:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 20:28 [PATCH] Fix Kconfig for Broadcom SWARM Manish Lachwani
2005-02-01 22:42 ` Maciej W. Rozycki
2005-02-01 22:54 ` Manish Lachwani
2005-02-01 23:27 ` Maciej W. Rozycki
2005-02-03 14:29 ` Ralf Baechle
2005-02-03 17:36 ` Manish Lachwani
2005-02-03 23:57 ` Ralf Baechle [this message]
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=20050203235702.GA22311@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mlachwani@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox