Linux-Wireless Archive on lore.kernel.org
 help / color / 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>,
	"briannorris@chromium.org" <briannorris@chromium.org>
Subject: RE: [PATCH 00/10] rtw88: minor throughput improvement
Date: Tue, 15 Oct 2019 03:23:10 +0000
Message-ID: <F7CD281DE3E379468C6D07993EA72F84D18FDB17@RTITMBSVM04.realtek.com.tw> (raw)
In-Reply-To: <87mue3fyoo.fsf@tynnyri.adurom.net>

> From: Kalle Valo 
> 
> <yhchuang@realtek.com> writes:
> 
> > From: Yan-Hsuan Chuang <yhchuang@realtek.com>
> >
> > This patchset mainly adds support for beamforming and power
> > tracking. Power tracking can monitor the thermal value of
> > the device and adjust corresponding power indexes, to make
> > sure the RF output power is expected.
> >
> > And another thing is to add a debugfs for physical layer
> > information. This is useful when sometimes the environment
> > is too harsh for the device, and provides the activities
> > for us to debug.
> >
> > The rest patches are some minor fixes.
> >
> >
> > Ping-Ke Shih (1):
> >   rtw88: coex: Set 4 slot mode for A2DP
> >
> > Tsang-Shian Lin (1):
> >   rtw88: add phy_info debugfs to show Tx/Rx physical status
> >
> > Tzu-En Huang (6):
> >   rtw88: add power tracking support
> >   rtw88: Enable 802.11ac beamformee support
> >   rtw88: config 8822c multicast address in MAC init flow
> >   rtw88: add set_bitrate_mask support
> >   rtw88: update regulatory settings implementaion
> >   rtw88: add NL80211_EXT_FEATURE_CAN_REPLACE_PTK0 support
> >
> > Yan-Hsuan Chuang (2):
> >   rtw88: Use rtw_write8_set to set SYS_FUNC
> >   rtw88: pci: config phy after chip info is setup
> 
> It would be easier for me if you could split the patchsets even more,
> for example fixes into one set and new features into another. That way I
> can apply the fixes faster. (I now applied five fixes from this set)
> 
> And maybe you could even split the new features into smaller sets, or
> maybe even just send them one by one once you have a patch ready
> (especially on bigger features). That would also make it faster to
> review, reviewing big patchsets is pain.
> 
> But whenever you submit, just to use wireless-drivers-next as the
> baseline, and no extra patches on top of. That way it's for git to
> handle conflicts.
> 

Sorry, it my fault to mess them into one patch set.
Will try to split them into more sets.
Thanks.

Yan-Hsuan

      reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08  8:20 yhchuang
2019-10-08  8:20 ` [PATCH 01/10] rtw88: add power tracking support yhchuang
2019-10-09  8:17   ` Kalle Valo
2019-10-08  8:20 ` [PATCH 02/10] rtw88: Enable 802.11ac beamformee support yhchuang
2019-10-14  9:38   ` Kalle Valo
2019-10-08  8:20 ` [PATCH 03/10] rtw88: config 8822c multicast address in MAC init flow yhchuang
2019-10-14  9:08   ` Kalle Valo
2019-10-08  8:20 ` [PATCH 04/10] rtw88: add set_bitrate_mask support yhchuang
2019-10-08  8:20 ` [PATCH 05/10] rtw88: update regulatory settings implementaion yhchuang
2019-10-14  9:39   ` Kalle Valo
2019-10-08  8:20 ` [PATCH 06/10] rtw88: add NL80211_EXT_FEATURE_CAN_REPLACE_PTK0 support yhchuang
2019-10-14  9:11   ` Kalle Valo
2019-10-08  8:20 ` [PATCH 07/10] rtw88: Use rtw_write8_set to set SYS_FUNC yhchuang
2019-10-08  8:20 ` [PATCH 08/10] rtw88: pci: config phy after chip info is setup yhchuang
2019-10-08  8:21 ` [PATCH 09/10] rtw88: coex: Set 4 slot mode for A2DP yhchuang
2019-10-08  8:21 ` [PATCH 10/10] rtw88: add phy_info debugfs to show Tx/Rx physical status yhchuang
2019-10-14  9:45 ` [PATCH 00/10] rtw88: minor throughput improvement Kalle Valo
2019-10-15  3:23   ` Tony Chuang [this message]

Reply instructions:

You may reply publically 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=F7CD281DE3E379468C6D07993EA72F84D18FDB17@RTITMBSVM04.realtek.com.tw \
    --to=yhchuang@realtek.com \
    --cc=briannorris@chromium.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /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

Linux-Wireless Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-wireless/0 linux-wireless/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-wireless linux-wireless/ https://lore.kernel.org/linux-wireless \
		linux-wireless@vger.kernel.org
	public-inbox-index linux-wireless

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-wireless


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git