<yhchuang@xxxxxxxxxxx> writes: > From: Yan-Hsuan Chuang <yhchuang@xxxxxxxxxxx> > > 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. -- https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
