(adding back linux-wireless, please don't drop CC) > Kalle Valo <[email protected]> 於 2019年7月15日週一 下午5:07寫道： >> >> Fuqian Huang <[email protected]> writes: >> >> > In commit 518a2f1925c3 >> > ("dma-mapping: zero memory returned from dma_alloc_*"), >> > dma_alloc_coherent has already zeroed the memory. >> > So memset is not needed. >> > >> > Signed-off-by: Fuqian Huang <[email protected]> >> > --- >> > Changes in v3: >> > - Use actual commit rather than the merge commit in the commit message >> > >> > drivers/net/wireless/ath/ath10k/ce.c | 5 ----- >> > drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c | 2 -- >> > drivers/net/wireless/quantenna/qtnfmac/pcie/pearl_pcie.c | 2 -- >> > drivers/net/wireless/quantenna/qtnfmac/pcie/topaz_pcie.c | 2 -- >> > 4 files changed, 11 deletions(-) >> >> Via which tree is this supposed to go? Can I take this to >> wireless-drivers-next? > > I think the wireless-drivers-next is fine.
Good, I'll then take these to my queue. > The four file have similar changes. And they are both under wireless > subsystem. How should i indicate which tree the patch should go to? > Should I mark them in [patch v3 wireless] or after the Changes in v3? > I should avoid this mistake next time. As there's no dependency between patches to me the easiest is that you send the wireless patches separately, that way I can take them directly without asking anything, and not worry about dependencies or if someone else is going to apply them. For example Colin King does that his cleanup patches and I like it a lot. But if I see patch 20/24 (and only that, no cover letter or over patches) I have no clue what the plan is and need extra effort to understand what I should do. -- Kalle Valo
