From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Andrei Gherzan <andrei@gherzan.ro>,
openembedded <openembedded-core@lists.openembedded.org>
Subject: Re: Linux firmware for iwlwifi 8000c disappeared in pyro
Date: Fri, 16 Feb 2018 15:23:39 +0200 [thread overview]
Message-ID: <cc978b8d-afa0-5ea2-ba5d-9700bab26fdc@linux.intel.com> (raw)
In-Reply-To: <CAK18fxEEZRnHzobX=Lt2By_VYgEzi36nSU+X_94Etegh8E81mg@mail.gmail.com>
On 02/16/2018 01:42 PM, Andrei Gherzan wrote:
> This happened because the removal of the 8000c-19 firmware patch in pyro
> removes the package completely as well
> (http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb?h=pyro&id=3e4b382c0c687a76f824cd84b478c4f778e15e3e).
> While the patch that ended up in master only removed that specific
> firmware
> (http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-kernel/linux-firmware/linux-firmware_git.bb?id=8d2e66817a6e5cea5a0146f2804e703402de44dc).
>
> Any idea why this happened? Can we bring back the package in pyro as well?
This looks like a simple mistake. Prepare (and test :) a patch to
correct it, and send it here with [pyro] prefix.
Alex
next prev parent reply other threads:[~2018-02-16 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 11:42 Linux firmware for iwlwifi 8000c disappeared in pyro Andrei Gherzan
2018-02-16 13:23 ` Alexander Kanavin [this message]
2018-02-16 13:48 ` Palleti, Avinash Reddy
2018-02-16 14:08 ` Andrei Gherzan
2018-02-20 12:50 ` Andrei Gherzan
2018-02-21 4:47 ` akuster808
2018-02-21 4:52 ` Palleti, Avinash Reddy
2018-02-26 8:16 ` Palleti, Avinash Reddy
2018-03-05 20:24 ` Denys Dmytriyenko
[not found] ` <20ae973a-1a8e-3950-193c-4adda84c513f@mvista.com>
2018-03-15 17:49 ` Denys Dmytriyenko
2018-03-15 21:10 ` akuster808
2018-03-23 20:57 ` akuster808
2018-03-23 21:19 ` Denys Dmytriyenko
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=cc978b8d-afa0-5ea2-ba5d-9700bab26fdc@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=andrei@gherzan.ro \
--cc=openembedded-core@lists.openembedded.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