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>,
Andrey Shevchenko <ashevchenko@quantenna.com>
Subject: Re: [PATCH v2 1/2] qtnfmac_pcie: use single PCIe driver for all platforms
Date: Tue, 6 Nov 2018 16:56:08 +0000 (UTC) [thread overview]
Message-ID: <20181106165608.DF4FE603D2@smtp.codeaurora.org> (raw)
In-Reply-To: <20181016102349.26544-2-sergey.matyukevich.os@quantenna.com>
Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> wrote:
> From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
>
> Single PCIe driver can identify hardware type by reading CHIP ID at
> probe time and invoking a correct initialization sequence.
>
> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
2 patches applied to wireless-drivers-next.git, thanks.
b7da53cd6cd1 qtnfmac_pcie: use single PCIe driver for all platforms
e401fa25cfa2 qtnfmac: add support for Topaz chipsets
--
https://patchwork.kernel.org/patch/10643355/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2018-11-06 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 10:23 [PATCH v2 0/2] qtnfmac: add support for QSR1000/QSR2000 (aka Topaz) chipsets Sergey Matyukevich
2018-10-16 10:23 ` [PATCH v2 1/2] qtnfmac_pcie: use single PCIe driver for all platforms Sergey Matyukevich
2018-11-06 16:56 ` Kalle Valo [this message]
2018-10-16 10:23 ` [PATCH v2 2/2] qtnfmac: add support for Topaz chipsets Sergey Matyukevich
2019-05-18 17:54 ` Jonas Gorski
2019-05-23 19:26 ` Igor Mitsyanko
2019-11-19 16:12 ` Jonas Gorski
2019-11-21 2:27 ` Igor Mitsyanko
2019-11-21 12:16 ` Kalle Valo
2019-11-22 14:35 ` Bjørn Mork
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=20181106165608.DF4FE603D2@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ashevchenko@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=linux-wireless@vger.kernel.org \
--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.