From: Kalle Valo <kvalo@codeaurora.org>
To: Tobias Schramm <tobleminer@gmail.com>
Cc: kvalo@qca.qualcomm.com, ath10k@lists.infradead.org,
linux-wireless@vger.kernel.org, bhelgaas@google.com,
linux-pci@vger.kernel.org, Tobias Schramm <tobleminer@gmail.com>
Subject: Re: [v3,2/2] ath10k: Add support for Ubiquiti rebranded QCA988X v2
Date: Mon, 29 Jan 2018 14:45:03 +0000 (UTC) [thread overview]
Message-ID: <20180129144503.6A5B4609EF@smtp.codeaurora.org> (raw)
In-Reply-To: <20180125111340.17553-3-tobleminer@gmail.com>
Tobias Schramm <tobleminer@gmail.com> wrote:
> Some modern Ubiquiti devices contain a rebranded QCA988X rev2 with
> a custom Ubiquiti vendor and device id. This patch adds support for
> those devices, treating them as a QCA988X v2.
>
> Signed-off-by: Tobias Schramm <tobleminer@gmail.com>
> [kvalo@codeaurora.org: rebase, add missing fields in hw_params, fix a long line in pci.c:61]
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
This didn't apply to ath.git so I rebased it and it did some other modifications
(list in the commit log):
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=pending&id=4037b395c946f94ee05ddc652421cdbd35567a3e
--
https://patchwork.kernel.org/patch/10183909/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-01-29 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 11:13 [PATCH v3 0/2] ath10k: Add support for Ubiquiti-branded QCA988X Tobias Schramm
2018-01-25 11:13 ` [PATCH v3 1/2] pci: Add vendor id of Ubiquiti Networks Tobias Schramm
2018-01-29 18:03 ` Bjorn Helgaas
2018-01-29 18:41 ` Kalle Valo
2018-02-07 14:11 ` [v3,1/2] " Kalle Valo
2018-01-25 11:13 ` [PATCH v3 2/2] ath10k: Add support for Ubiquiti rebranded QCA988X v2 Tobias Schramm
2018-01-29 14:45 ` Kalle Valo [this message]
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=20180129144503.6A5B4609EF@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=bhelgaas@google.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tobleminer@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).