From: Stanislaw Gruszka <sgruszka@redhat.com>
To: "Valo, Kalle" <kvalo@qca.qualcomm.com>
Cc: "Yijun_Shen@Dell.com" <Yijun_Shen@dell.com>,
"michal.kazior@tieto.com" <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"perry_yuan@dell.com" <perry_yuan@dell.com>
Subject: Re: ath10k fail to load firmware
Date: Mon, 22 Aug 2016 13:02:14 +0200 [thread overview]
Message-ID: <20160822110214.GB2118@redhat.com> (raw)
In-Reply-To: <87mvk5xfjw.fsf@kamboji.qca.qualcomm.com>
On Mon, Aug 22, 2016 at 10:29:24AM +0000, Valo, Kalle wrote:
> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>
> > On Tue, Aug 02, 2016 at 12:10:46PM +0000, Valo, Kalle wrote:
> >> I pushed a new board-2.bin:
> >>
> >> https://github.com/kvalo/ath10k-firmware/commit/7c0411643b195b246d3871f409f9219f528b39c1
> >
> > Kalle, when do you plan to propagate this to upstream linux-firmware ?
>
> I usually send firmware updates to linux-firmware in a bigger update. I
> have quite a lot of patches pending so I wasn't planning to do it quite
> not yet.
>
> Why are you asking, is this urgent?
Well, we want to add support to Dell ath10k devices to our system,
but we are also a bit reluctant to have difference between
linux-firmware package in our system and upstream linux-firmware
git tree. Could you post just board-2.bin changes upstream soon ?
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-08-22 11:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 7:09 ath10k fail to load firmware Stanislaw Gruszka
2016-07-19 7:18 ` Michal Kazior
2016-07-19 7:27 ` Stanislaw Gruszka
2016-07-19 8:07 ` Perry_Yuan
2016-07-19 8:24 ` Perry_Yuan
2016-07-19 8:32 ` Michal Kazior
2016-07-19 9:02 ` Perry_Yuan
2016-07-19 9:17 ` Michal Kazior
2016-07-19 9:27 ` Stanislaw Gruszka
2016-07-19 9:41 ` Perry_Yuan
2016-07-20 3:14 ` Perry_Yuan
2016-07-20 6:58 ` Michal Kazior
2016-07-20 7:23 ` Perry_Yuan
[not found] ` <A3D794F1192BBF449DF2EC3D7EE263F44A5402F40A@SHAX7MCDC101.APAC.DELL.COM>
2016-07-25 10:25 ` Michal Kazior
2016-08-02 12:19 ` Valo, Kalle
2016-07-29 7:45 ` Perry_Yuan
2016-07-29 9:07 ` Perry_Yuan
2016-08-02 12:10 ` Valo, Kalle
2016-08-03 7:00 ` Michal Kazior
2016-08-22 8:40 ` Stanislaw Gruszka
2016-08-22 10:29 ` Valo, Kalle
2016-08-22 11:02 ` Stanislaw Gruszka [this message]
2016-08-22 14:05 ` Valo, Kalle
2016-08-23 18:55 ` Valo, Kalle
2016-08-24 6:33 ` Stanislaw Gruszka
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=20160822110214.GB2118@redhat.com \
--to=sgruszka@redhat.com \
--cc=Yijun_Shen@dell.com \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.com \
--cc=michal.kazior@tieto.com \
--cc=perry_yuan@dell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.