From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dmitri Vorobiev <dmitri.vorobiev@movial.fi>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 6
Date: Fri, 6 Jun 2008 21:11:51 +1000 [thread overview]
Message-ID: <20080606211151.b36ed703.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4848F9E5.20005@movial.fi>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hi Dmitri,
On Fri, 06 Jun 2008 11:48:37 +0300 Dmitri Vorobiev <dmitri.vorobiev@movial.fi> wrote:
>
> Please see http://lkml.org/lkml/2008/6/4/152 where you'll find the
> description of how I built a MIPS cross-toolchain and a working MIPS config.
Thanks for that. Sorry I didn't respond sooner.
We have managed to make a working tool chain and I will
add some MIPS builds soon. Was the attached config just the
malta_defconfig in the kernel tree, or there something special about it.
I noticed that a straight defconfig build works for mips and mipsel.
Would you expect all{no,mod}config to work? What would be a good 64 bit
test config?
It is easier for us if we just use the configs out of the kernel tree,
but others are possible (its just harder to keep them up to date).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-06 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 8:35 linux-next: Tree for June 6 Stephen Rothwell
2008-06-06 8:48 ` Dmitri Vorobiev
2008-06-06 11:11 ` Stephen Rothwell [this message]
2008-06-06 14:42 ` Dmitri Vorobiev
-- strict thread matches above, loose matches on Subject: below --
2011-06-06 3:20 Stephen Rothwell
2011-06-07 9:48 ` Catalin Marinas
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=20080606211151.b36ed703.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dmitri.vorobiev@movial.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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