linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/4] wifi: rtw89: read version of analog hardware
Date: Fri, 14 Apr 2023 12:24:02 +0000 (UTC)	[thread overview]
Message-ID: <168147504062.16522.2962599599283522309.kvalo@kernel.org> (raw)
In-Reply-To: <20230330133324.19538-2-pkshih@realtek.com>

Ping-Ke Shih <pkshih@realtek.com> wrote:

> The chip contains digital and analog parts, and each of them has its own
> version number. This is used by BT coexistence mechanism to make strategy
> decision for different analog version.
> 
> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com>

4 patches applied to wireless-next.git, thanks.

a6fb2bb84654 wifi: rtw89: read version of analog hardware
d5289b2d69a7 wifi: rtw89: 8851b: fix TX path to path A for one RF path chip
5c3afcba545c wifi: rtw89: mac: update MAC settings to support 8851b
2a6d518dedcb wifi: rtw89: pci: update PCI related settings to support 8851B

-- 
https://patchwork.kernel.org/project/linux-wireless/patch/20230330133324.19538-2-pkshih@realtek.com/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  reply	other threads:[~2023-04-14 12:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 13:33 [PATCH 0/4] wifi: rtw89: 8851b: adjust shared code to support 8851B Ping-Ke Shih
2023-03-30 13:33 ` [PATCH 1/4] wifi: rtw89: read version of analog hardware Ping-Ke Shih
2023-04-14 12:24   ` Kalle Valo [this message]
2023-03-30 13:33 ` [PATCH 2/4] wifi: rtw89: 8851b: fix TX path to path A for one RF path chip Ping-Ke Shih
2023-03-30 13:33 ` [PATCH 3/4] wifi: rtw89: mac: update MAC settings to support 8851b Ping-Ke Shih
2023-03-30 13:33 ` [PATCH 4/4] wifi: rtw89: pci: update PCI related settings to support 8851B Ping-Ke Shih

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=168147504062.16522.2962599599283522309.kvalo@kernel.org \
    --to=kvalo@kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pkshih@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).