From: Michal Marek <mmarek@suse.cz>
To: Ronald <ronald645@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Regression: firmware: Simplify directory creation + b43 = fails to build
Date: Wed, 18 Jun 2014 16:33:56 +0200 [thread overview]
Message-ID: <53A1A354.7030107@suse.cz> (raw)
In-Reply-To: <CAF1_xX2oeG0YCLaLZR9ZUY2qiD0-sVB6L10dZppnae7iZV_U3g@mail.gmail.com>
Dne 18.6.2014 10:46, Ronald napsal(a):
> Dear kernel developers,
>
> Latest git HEAD (from Torvalds):
>
> CC drivers/base/firmware_class.o
> LD drivers/base/built-in.o
> MK_FW firmware/b43/ucode5.fw.gen.S
> /bin/sh: firmware/b43/ucode5.fw.gen.S: Bestand of map bestaat niet
> (file or directory does not exist, it should not have the .gen.S
> suffix)
> /bin/sh: firmware/b43/ucode5.fw.gen.S: Bestand of map bestaat niet
> ... snip ...
> /bin/sh: firmware/b43/ucode5.fw.gen.S: Bestand of map bestaat niet
> firmware/Makefile:185: recept voor doel 'firmware/b43/ucode5.fw.gen.S'
> is mislukt
> make[1]: *** [firmware/b43/ucode5.fw.gen.S] Fout 1
> Makefile:893: recept voor doel 'firmware' is mislukt
> make: *** [firmware] Fout 2
> make: *** Wachten op onvoltooide taken...
Where does firmware/b43 come from?
Thanks,
Michal
next prev parent reply other threads:[~2014-06-18 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 8:46 Regression: firmware: Simplify directory creation + b43 = fails to build Ronald
2014-06-18 14:33 ` Michal Marek [this message]
2014-06-18 16:25 ` Ronald
2014-07-07 19:02 ` Torsten Kaiser
2014-07-08 12:09 ` Michal Marek
2014-07-08 12:47 ` [PATCH] firmware: Create directories for external firmware Michal Marek
[not found] ` <CAF1_xX19AwepGJLJOcn_m+OaU3kk9N9d+M2v_YzzPg-M2cdrPQ@mail.gmail.com>
2014-07-08 15:19 ` Ronald
2014-07-08 16:29 ` Ronald
2014-07-08 18:03 ` Torsten Kaiser
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=53A1A354.7030107@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ronald645@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox