From: Kalle Valo <kvalo@codeaurora.org>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
Mikhail Karpenko <mkarpenko@quantenna.com>,
Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Subject: Re: [PATCH 01/10] qtnfmac: use MAJOR.MINOR format for firmware protocol
Date: Wed, 12 Feb 2020 16:17:23 +0000 (UTC) [thread overview]
Message-ID: <20200212161723.8B211C4479F@smtp.codeaurora.org> (raw)
In-Reply-To: <20200127104634.7248-2-sergey.matyukevich.os@quantenna.com>
Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> wrote:
> From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
>
> Use MAJOR.MINOR format for QLink firmware protocol. MAJOR part is
> incremented when backward compatibility is broken. Normally this
> part should not be incremented unless there is a good reason for
> that. MINOR part is incremented each time when new features are
> added to qlink.h, e.g. new TLVs, events, commands. These changes
> should not break backward compatibility. For instance, older
> firmware versions may not be able to parse new flags or send new
> types of events, but this does not impact normal system operations.
>
> As part of initialization sequence, driver requests protocol version
> from firmware and refuses to start in case there is a mismatch in MAJOR
> part of the version.
>
> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
10 patches applied to wireless-drivers-next.git, thanks.
a3ebb0335c54 qtnfmac: use MAJOR.MINOR format for firmware protocol
310cd5dd5070 qtnfmac: pass hardware capabilities in TLV element
e70cf22bc7b2 qtnfmac: merge PHY_PARAMS_GET into MAC_INFO
bc5db734c1c4 qtnfmac: drop QTN_TLV_ID_NUM_IFACE_COMB TLV type
601ce21ff88d qtnfmac: implement extendable channel survey dump
0d18a9c0a387 qtnfmac: pass max scan SSIDs limit on per-radio basis
8b0b5f1ba9e0 qtnfmac: cleanup alignment in firmware communication protocol
5edadc5a3f11 qtnfmac: update channel switch command to support 6GHz band
501c3be1ec3c qtnfmac: drop unnecessary TLVs from scan command
946d077a4256 qtnfmac: fix potential Spectre vulnerabilities
--
https://patchwork.kernel.org/patch/11352415/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-02-12 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 10:46 [PATCH 00/10] qtnfmac: update firmware protocol Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 01/10] qtnfmac: use MAJOR.MINOR format for " Sergey Matyukevich
2020-02-12 16:17 ` Kalle Valo [this message]
2020-01-27 10:46 ` [PATCH 02/10] qtnfmac: pass hardware capabilities in TLV element Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 03/10] qtnfmac: merge PHY_PARAMS_GET into MAC_INFO Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 04/10] qtnfmac: drop QTN_TLV_ID_NUM_IFACE_COMB TLV type Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 05/10] qtnfmac: implement extendable channel survey dump Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 06/10] qtnfmac: pass max scan SSIDs limit on per-radio basis Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 07/10] qtnfmac: cleanup alignment in firmware communication protocol Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 08/10] qtnfmac: update channel switch command to support 6GHz band Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 09/10] qtnfmac: drop unnecessary TLVs from scan command Sergey Matyukevich
2020-01-27 10:46 ` [PATCH 10/10] qtnfmac: fix potential Spectre vulnerabilities Sergey Matyukevich
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=20200212161723.8B211C4479F@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mkarpenko@quantenna.com \
--cc=sergey.matyukevich.os@quantenna.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.