linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Chuang <yhchuang@realtek.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Andy Huang" <tehuang@realtek.com>,
	"bigeasy@linutronix.de" <bigeasy@linutronix.de>
Subject: RE: [PATCH v2] rtw88: 8821c: coex: add functions and parameters
Date: Mon, 20 Jul 2020 09:15:19 +0000	[thread overview]
Message-ID: <33152a8d95804ef5bb68579c8b40ebe3@realtek.com> (raw)
In-Reply-To: <87lfje7dv1.fsf@codeaurora.org>

> <yhchuang@realtek.com> writes:
> 
> > From: Ping-Cheng Chen <pc.chen@realtek.com>
> >
> > Without this patch, RTL8821CE will not have coex support,
> > and will crash the system because of the NULL pointers
> > for the coex functions.
> >
> > While RTL8822C series are WiFi + BT combo chips, it needs
> > the co-existence mechanism for the device to work on both
> > WiFi and BT without interfering each other. And the coex
> > support has already been added before, most of the mechanisms
> > are implemented. The driver should just add corresponding
> > functions to operate on different types of chips and its
> > coex parameters.
> >
> > Fixes: f745eb9ca5bf ("rtw88: 8821c: Add 8821CE to Kconfig and Makefile")
> > Signed-off-by: Ping-Cheng Chen <pc.chen@realtek.com>
> > Signed-off-by: Tzu-En Huang <tehuang@realtek.com>
> > Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
> 
> What changed from v1?
> 

Just the name of the author, nothing else :)

Yen-Hsuan

      reply	other threads:[~2020-07-20  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20  2:09 [PATCH v2] rtw88: 8821c: coex: add functions and parameters yhchuang
2020-07-20  9:08 ` Kalle Valo
2020-07-20  9:15   ` Tony Chuang [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=33152a8d95804ef5bb68579c8b40ebe3@realtek.com \
    --to=yhchuang@realtek.com \
    --cc=bigeasy@linutronix.de \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tehuang@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 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).