From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] linux-firmware: drop revision handling for iwlwifi
Date: Tue, 19 Apr 2016 11:34:19 -0300 [thread overview]
Message-ID: <571641EB.6030305@zacarias.com.ar> (raw)
In-Reply-To: <20160417223047.5b2b76fa@free-electrons.com>
On 17/04/16 17:30, Thomas Petazzoni wrote:
> It would be nicer if we could find a way of using wildcards here, as it
> would make it more future proof (i.e it would automatically handle new
> firmware revisions).
>
> Could you have a look and see if it's doable?
Hi.
Switching the "tar -C $(@D) ..." to "cd $(@D); tar ... " in
LINUX_FIRMWARE_INSTALL_FILES makes it doable.
I'll send a new series shortly.
Regards.
prev parent reply other threads:[~2016-04-19 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 18:11 [Buildroot] [PATCH 1/2] linux-firmware: drop revision handling for iwlwifi Gustavo Zacarias
2016-04-15 18:11 ` [Buildroot] [PATCH 2/2] linux-firmware: add support for intel iwlwifi 7265D Gustavo Zacarias
2016-04-17 20:30 ` [Buildroot] [PATCH 1/2] linux-firmware: drop revision handling for iwlwifi Thomas Petazzoni
2016-04-19 14:34 ` Gustavo Zacarias [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=571641EB.6030305@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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