From: Alan Cox <alan@lxorguk•ukuu.org.uk>
To: Zimny Lech <napohybelskurwysynom2010@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for November 19
Date: Fri, 19 Nov 2010 17:42:57 +0000 [thread overview]
Message-ID: <20101119174257.58bb8e32@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTik6Aq+kWzpmYckKkV5yVMFPt-J0E7OMM6Rd4ouO@mail.gmail.com>
On Fri, 19 Nov 2010 18:40:41 +0100
Zimny Lech <napohybelskurwysynom2010@gmail•com> wrote:
> Salve,
>
> 2010/11/19 Stephen Rothwell <sfr@canb•auug.org.au>:
> > Hi all,
> >
> > Changes since 20101118:
>
> This probably should not be available on x86_64
>
> BLD FW drivers/net/wan/wanxlfw.inc
> /bin/sh: as68k: command not found
> /home/test/linux-2.6/drivers/net/wan/wanxlfw.S:39:0: fatal error: when
> writing output to : Broken pipe
> compilation terminated.
> make[4]: *** [drivers/net/wan/wanxlfw.inc] Error 127
If you want to build the wanxl firmware then you need the m68k assembler
for the firmware, so it is right.
next prev parent reply other threads:[~2010-11-19 17:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 3:32 linux-next: Tree for November 19 Stephen Rothwell
2010-11-19 17:15 ` linux-next: Tree for November 19 (sched_fair) Randy Dunlap
2010-11-19 17:16 ` linux-next: Tree for November 19 (rtmutex) Randy Dunlap
2010-12-02 19:52 ` Randy Dunlap
2010-11-19 17:30 ` [PATCH -next] staging: fix winbond build, needs delay.h Randy Dunlap
2010-11-19 17:37 ` Pavel Machek
2010-11-19 17:38 ` Greg KH
2010-11-19 17:48 ` Randy Dunlap
2010-11-19 17:54 ` Greg KH
2010-11-19 17:40 ` linux-next: Tree for November 19 Zimny Lech
2010-11-19 17:42 ` Alan Cox [this message]
2010-11-19 18:35 ` Zimny Lech
2010-11-20 5:50 ` Zimny Lech
2010-11-20 5:52 ` Zimny Lech
2010-11-20 10:44 ` Jens Axboe
2010-11-20 7:15 ` Zimny Lech
-- strict thread matches above, loose matches on Subject: below --
2009-11-19 7:44 Stephen Rothwell
2008-11-19 6:59 Stephen Rothwell
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=20101119174257.58bb8e32@lxorguk.ukuu.org.uk \
--to=alan@lxorguk$(echo .)ukuu.org.uk \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=napohybelskurwysynom2010@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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