All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: yhchuang@realtek.com, Larry.Finger@lwfinger.net,
	linux-wireless@vger.kernel.org, pkshih@realtek.com,
	tehuang@realtek.com
Subject: Re: [PATCH v2 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips
Date: Thu, 13 Dec 2018 11:48:32 +0200	[thread overview]
Message-ID: <87bm5pzrin.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20181212090743.GA13331@redhat.com> (Stanislaw Gruszka's message of "Wed, 12 Dec 2018 10:07:43 +0100")

Stanislaw Gruszka <sgruszka@redhat.com> writes:

> On Fri, Nov 16, 2018 at 07:31:06PM +0800, yhchuang@realtek.com wrote:
>> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>> 
>> This is a new mac80211 driver for Realtek 802.11ac wireless network chips.
>> rtw88 supports 8822BE and 8822CE chips, and will be able to support
>> multi-vif combinations in run-time.
>> 
>> For now, only PCI bus is supported, but rtw88 was originally designed
>> to optionally support three buses includes USB & SDIO. USB & SDIO modules
>> will soon be supported by rtw88, with configurable core module to fit
>> with different bus modules in the same time.
>
> Kalle, is here anything that stop the driver being merged ?

First of all, thanks for reviewing this. It helps a lot.

Before I'm willing to apply this needs review both from Johannes and me.
And of course some build testing in pending branch, I'll try to setup
that ASAP.

-- 
Kalle Valo

  reply	other threads:[~2018-12-13  9:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 11:31 [PATCH v2 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips yhchuang
2018-11-16 11:31 ` [PATCH v2 01/13] rtw88: main files yhchuang
2018-12-07  8:23   ` Tony Chuang
2018-12-13  9:46     ` Kalle Valo
2018-11-16 11:31 ` [PATCH v2 02/13] rtw88: core files yhchuang
2018-11-16 11:31 ` [PATCH v2 03/13] rtw88: hci files yhchuang
2018-11-16 11:31 ` [PATCH v2 04/13] rtw88: trx files yhchuang
2018-11-16 11:31 ` [PATCH v2 05/13] rtw88: mac files yhchuang
2018-11-16 11:31 ` [PATCH v2 06/13] rtw88: fw and efuse files yhchuang
2018-11-16 11:31 ` [PATCH v2 07/13] rtw88: phy files yhchuang
2018-11-16 11:31 ` [PATCH v2 08/13] rtw88: debug files yhchuang
2018-11-16 11:31 ` [PATCH v2 09/13] rtw88: chip files yhchuang
2018-11-16 11:31 ` [PATCH v2 10/13] rtw88: 8822B init table yhchuang
2018-11-16 11:31 ` [PATCH v2 11/13] rtw88: 8822C " yhchuang
2018-11-16 11:31 ` [PATCH v2 12/13] rtw88: Kconfig & Makefile yhchuang
2018-11-16 11:31 ` [PATCH v2 13/13] rtw88: add support for Realtek 802.11ac wireless chips yhchuang
2019-01-22 21:34   ` Brian Norris
2019-01-28  3:36     ` Tony Chuang
2019-01-28 21:01       ` Brian Norris
2019-01-29  8:59         ` Kalle Valo
2018-11-30  9:37 ` [PATCH v2 00/13] rtw88: mac80211 driver for Realtek 802.11ac wireless network chips Stanislaw Gruszka
2018-12-12  9:07 ` Stanislaw Gruszka
2018-12-13  9:48   ` Kalle Valo [this message]
2019-01-08  2:48     ` Tony Chuang

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=87bm5pzrin.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@realtek.com \
    --cc=sgruszka@redhat.com \
    --cc=tehuang@realtek.com \
    --cc=yhchuang@realtek.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.