> -----Original Message----- > From: Kalle Valo [mailto:kvalo@xxxxxxxxxxxxxx] > Sent: Thursday, May 30, 2019 1:11 PM > To: Tony Chuang > Cc: Larry Finger; linux-wireless@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 01/11] rtw88: resolve order of tx power setting routines > > Tony Chuang <yhchuang@xxxxxxxxxxx> writes: > > >> > These patches are based on > >> > > >> > > >> > https://kernel.googlesource.com/pub/scm/linux/kernel/git/kvalo/wireless-dr > >> ivers > >> > branch master > >> > > >> > commit 6aca09771db4277a78853d6ac680d8d5f0d915e3 > >> > Author: YueHaibing <yuehaibing@xxxxxxxxxx> > >> > Date: Sat May 4 18:32:24 2019 +0800 > >> > > >> > rtw88: Make some symbols static > >> > > >> > > >> > It should apply, did I miss something? > >> > >> I keep the bar high and take to wireless-drivers only patches which fix > >> important, user visible problems. Everything else goes to > >> wireless-drivers-next. So you should use wireless-drivers-next as the > >> baseline for all regular patches. > > > > But this series has dependency with " rtw88: Make some symbols static" > > This is exactly why I keep the bar high for patches going to > wireless-drivers :) These depencies and conflicts are just too time > consuming otherwise. > > > Or you can handle it > > Unfortunately not, as I made a mistake when fast-forwarding > wireless-drivers and I cannot merge wireless-drivers into > wireles-drivers-next right now. So you just need to wait for the > depencies to trickle down to w-d-next, that will take few weeks. It means that I just need to wait for the patches in w-d to go to w-d-next? So I don't need to resend them, just wait and you can merge this. Yan-Hsuan
