Hi Stefan, stefan@xxxxxxxxxxxxxxxxxx wrote on Sat, 18 May 2024 23:49:41 +0200: > Hello Miquel, > > On 13.05.24 09:09, Miquel Raynal wrote: > > Hi Dmitry, > > > > + Stefan > > > > dmantipov@xxxxxxxxx wrote on Wed, 8 May 2024 14:40:10 +0300: > > > >> Since 'symbol_duration' of 'struct wpan_phy' is in nanoseconds but > >> 'lifs_period' and 'sifs_period' are both in microseconds, fix time > >> calculation in 'ieee802154_configure_durations()' and use convenient > >> 'NSEC_PER_USEC' in 'ieee802154_setup_wpan_phy_pib()' as well. > >> Compile tested only. > >> > >> Found by Linux Verification Center (linuxtesting.org) with SVACE. > >> > > > > Requires Fixes and Cc: stable I guess. > > Fixes should be enough to get picked up. Added before pushing. Actually, unless the process changed recently, IIRC we should add Cc: stable when we think it should be backported (like this patch). The stable team indeed introduced an algorithm to collect patches not flagged with this tag "by mistake", but they ask us to continue Cc'ing them. Of course a Fixes tag is a good hint for the algorithm that the patch should be backported, and most of the time the patch will be backported anyway. Also rules being often different in net/, I think even net maintainers now comply with this and not longer do the cherry-picks themselves. But maybe this changed recently again and my just lost :-) Thanks, Miquèl
