Hi Jakub, >> The following changes since commit 8aaaf2f3af2ae212428f4db1af34214225f5cec3: >> >> Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2022-01-09 17:00:17 -0800) >> >> are available in the Git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git tags/for-net-next-2022-01-28 >> >> for you to fetch changes up to 91cb4c19118a19470a9d7d6dbdf64763bbbadcde: >> >> Bluetooth: Increment management interface revision (2022-01-27 12:35:13 -0800) >> >> ---------------------------------------------------------------- >> bluetooth-next pull request for net-next: >> >> - Add support for RTL8822C hci_ver 0x08 >> - Add support for RTL8852AE part 0bda:2852 >> - Fix WBS setting for Intel legacy ROM products >> - Enable SCO over I2S ib mt7921s >> - Increment management interface revision > > Thanks for fixing the warnings! :) > > I presume this is for the net-next given the name of your tree, but > a lot of patches here have fixes tags. What's your methodology on > separating fixes from new features? > > I think it may be worth adjusting the filter there and send more > stuff earlier to Linus's tree. Especially fixes with the right mix > of confidence and impact or pure device ID additions. > > To be clear - happy to pull this PR as is, I was meaning to ask about > this for a while. we started to add Fixes: tag whenever you can identify a faulty commit or can track down the original issue. This way we can later easily go back and check. It have to note that a lot of vendor trees cherrypick patches and this helps them picking the right ones. I reviewed the list of patches again, and frankly none of them are super critical to go to Linus right away. So if you don’t mind, please pull. Regards Marcel
