Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k_htc: force FW v1.4.0
Date: Thu, 12 Mar 2015 16:02:39 +0200	[thread overview]
Message-ID: <87bnjytitc.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <54FF5431.3020708@rempel-privat.de> (Oleksij Rempel's message of "Tue, 10 Mar 2015 21:29:37 +0100")

Oleksij Rempel <linux@rempel-privat.de> writes:

> Am 10.03.2015 um 16:35 schrieb Adrian Chadd:
>> Yeah, let's have it warn for a month or two.
>> 
>> There's some pending work that will break the API with 1.3 firmware,
>> so it has to happen sooner rather than later. But yeah, maybe warn for
>> about a month would be good. the older firmware is still in the git
>> tree in case people want it.
>
> I'm not sure if warning patch will do the trick.
> Let me resend this patch in one or two months. Are you ok with it?
> Like Adrian said, there are pending patches (since 2013) which will
> brake compatibility with 1.3

Yeah, that's better. The crystall ball[1] says that 4.2 will be released
in August, that should be plenty of time for user space to catch up. So
if you resend this end of April or so the patch should go to 4.2.

[1] http://phb-crystal-ball.org/

-- 
Kalle Valo

  reply	other threads:[~2015-03-12 14:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 19:38 [ath9k-devel] [PATCH] ath9k_htc: force FW v1.4.0 Oleksij Rempel
2015-03-10  8:11 ` Kalle Valo
2015-03-10 15:35   ` Adrian Chadd
2015-03-10 20:29     ` Oleksij Rempel
2015-03-12 14:02       ` Kalle Valo [this message]
2015-03-12 19:38         ` Adrian Chadd

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=87bnjytitc.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath9k-devel@lists.ath9k.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