public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@googlemail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: Lauri Kasanen <cand@gmx.com>, linux-wireless@vger.kernel.org
Subject: Re: [RESEND] Re: updating carl9170-1.fw in linux-firmware.git
Date: Thu, 19 May 2016 15:55:30 +0200	[thread overview]
Message-ID: <5231682.U0x3GAUzZo@debian64> (raw)
In-Reply-To: <87wpmqdwlh.fsf@kamboji.qca.qualcomm.com>

On Thursday, May 19, 2016 04:08:10 PM Kalle Valo wrote:
> Lauri Kasanen <cand@gmx.com> writes:
> 
> > On Tue, 03 May 2016 15:09:39 +0200
> > Christian Lamparter <chunkeey@googlemail.com> wrote:
> >
> >> On Thursday, April 21, 2016 03:22:15 PM Kalle Valo wrote:
> >> > Christian Lamparter <chunkeey@googlemail.com> writes:
> >> > 
> >> > > Maintainers. So for those people reading the fw list:
> >> > >
> >> > > What would it take to update the carl9170-1.fw firmware file in your
> >> > > repository to the latest version?
> >> > 
> >> > Thanks for following up on this. It would be good to solve this finally.
> >> Well, this was almost two weeks and no update yet.
> >> Kalle, can you please apply the "[PATCH v2] carl9170: Clarify kconfig text"
> >> patch from "Lauri Kasanen <cand@gmx.com>" [0].
> >> 
> >> [0] <https://marc.info/?l=linux-wireless&m=146081633405880>
> >
> > Seems we missed 4.7?
> 
> Yeah, I didn't consider this important enough and delayed it due to lack
> of time. I now put the patch back to my queue for 4.8, but please check
> that it's the correct version:
> 
> https://patchwork.kernel.org/patch/8861621/
Yes, this links to v2, which is the correct version.
 
> But we really should figure out how to get the latest version to
> linux-firmware, this is not good in the long run.
Well, none of my firmware patches were added/accepted and nobody
responded on how to add it to linux-firmware. I'm open for ideas.

Regards,
Christan

  reply	other threads:[~2016-05-19 13:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-16  8:33 [PATCH] carl9170: Clarify kconfig text Lauri Kasanen
     [not found] ` <1466768.7dLuLFSDol@debian64>
2016-04-16 14:18   ` [PATCH v2] " Lauri Kasanen
2016-04-16 15:32     ` Christian Lamparter
2016-04-18 15:45     ` Kalle Valo
2016-04-18 16:07       ` [PATCH v3] " Lauri Kasanen
2016-04-18 16:24         ` Christian Lamparter
2016-04-18 16:20       ` [PATCH v2] " Christian Lamparter
2016-04-18 16:42         ` Kalle Valo
2016-04-18 17:07           ` Christian Lamparter
2016-04-20  7:59             ` Kalle Valo
2016-04-20 21:11               ` [RESEND] Re: updating carl9170-1.fw in linux-firmware.git Christian Lamparter
     [not found]                 ` <87wpnrcft4.fsf@kamboji.qca.qualcomm.com>
     [not found]                   ` <54163090.DmVClckc2L@debian64>
2016-05-18  8:48                     ` Lauri Kasanen
2016-05-19 13:08                       ` Kalle Valo
2016-05-19 13:55                         ` Christian Lamparter [this message]
2016-05-20 18:18                 ` Xose Vazquez Perez
2016-05-25 14:51                 ` [RESEND] " Ben Hutchings
2016-06-04 14:58     ` [v2] carl9170: Clarify kconfig text Kalle Valo

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=5231682.U0x3GAUzZo@debian64 \
    --to=chunkeey@googlemail.com \
    --cc=cand@gmx.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.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