From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Daniel Jacobowitz <drow@false.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH] Bring the SWARM defconfig up to date
Date: Sat, 3 May 2008 07:44:24 +0100 [thread overview]
Message-ID: <20080503064424.GA15574@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0805030008280.12296@cliff.in.clinika.pl>
On Sat, May 03, 2008 at 12:48:45AM +0100, Maciej W. Rozycki wrote:
> The SWARM defconfig file has not been regenerated for over a year now.
> Here is a patch to bring the file up to date. Additionally some important
> and sometimes confusing changes happened meanwhile. Here is the list of
> notable corresponding updates to the configuration:
>
> 1. CPU_SB1_PASS_2_2 is now selected rather than CPU_SB1_PASS_1. The
> latter requires a non-standard -msb1-pass1-workarounds option to be
> supported by GCC and I am told is quite rare anyway.
Farely rare is a nice way to express it. The option exists in MV's
gcc 3.0 and as you know gcc 3.0 is no longer suitable to build a kernel ...
Ralf
prev parent reply other threads:[~2008-05-03 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 23:48 [PATCH] Bring the SWARM defconfig up to date Maciej W. Rozycki
2008-05-03 6:44 ` 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=20080503064424.GA15574@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=drow@false.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@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