Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> writes: > Hello Kalle, > > On Thu, Jun 01, 2023 at 12:17:44PM +0300, Kalle Valo wrote: >> Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> writes: >> >> > the motivation for this series is patch #3, patch #2 is a preparation for it >> > and patches #1 and #4 are just cleanups that I noticed en passant. >> > >> > Best regards >> > Uwe >> > >> > Uwe Kleine-König (4): >> > ath10k: Drop cleaning of driver data from probe error path and remove >> > ath10k: Drop checks that are always false >> > ath10k: Convert to platform remove callback returning void >> > atk10k: Don't opencode ath10k_pci_priv() in ath10k_ahb_priv() >> > >> > drivers/net/wireless/ath/ath10k/ahb.c | 20 +++----------------- >> > drivers/net/wireless/ath/ath10k/snoc.c | 8 +++----- >> > 2 files changed, 6 insertions(+), 22 deletions(-) >> >> ath10k patches go to my ath.git tree, not net-next. > > This isn't obvious for outsiders. Not sure what can be improved to > make this easier to spot. Yeah, you are definitely not the first one who is bitten by this. We do have the tree documented in MAINTAINERS but that's easy to miss: QUALCOMM ATHEROS ATH10K WIRELESS DRIVER M: Kalle Valo <kvalo@xxxxxxxxxx> L: ath10k@xxxxxxxxxxxxxxxxxxx S: Supported W: https://wireless.wiki.kernel.org/en/users/Drivers/ath10k T: git git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git F: Documentation/devicetree/bindings/net/wireless/qcom,ath10k.yaml F: drivers/net/wireless/ath/ath10k/ And a rule of thumb is that all wireless patches do normally go to wireless or wireless-next trees, and for most active wireless drivers we have separate trees as well (like ath.git in this case). -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
