On 2/21/2025 4:17 AM, Johannes Berg wrote: > Hi, > > I couldn't (yet?) figure out how to make the nipa bot stuff run > properly, so please start using > > [PATCH wireless] wifi: xyz > > or > > [PATCH wireless-next] wifi: xyz > > for the subject line. This way the automation can pick it up, see e.g. > > https://patchwork.kernel.org/project/linux-wireless/list/?series=936374 > > I'll need to fix some username stuff etc. > > I likely also need to add more trees to it - please reply with your > subject tags, trees and branches to use, e.g. > > wireless: main > https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git/ > > wireless-next: main > https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/ > > but perhaps we want to have > > rtw-next: rtw-next > https://github.com/pkshih/rtw > > or so? Not sure if you maintain a fixes branch there too? > > > Anyway, good luck to me, and please don't try to attack it ;-) I spent > all day setting it up, and haven't pulled out everything yet. First of all, thank you for adding any automation which improves the lives of the maintainers. Aditya has been working on that for the ath.git tree as well. ath.git contains both ath-current and ath-next branches in the same tree: https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/log/?h=ath-current https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git/log/?h=ath-next So we can use: [PATCH ath] for current (this branch gets little use) [PATCH ath-next] for next if that helps your automation. And for Qualcomm contributions we've been asking the developers to always supply a base: hash to also denote the basis of a patchset. /jeff
