On Thu, 22 May 2025 13:02:43 -0400 Luiz Augusto von Dentz wrote:
> > On Wed, 21 May 2025 10:47:55 -0400 Luiz Augusto von Dentz wrote:
> > > The following changes since commit e6b3527c3b0a676c710e91798c2709cc0538d312:
> > >
> > > Merge branch 'net-airoha-add-per-flow-stats-support-to-hw-flowtable-offloading' (2025-05-20 20:00:55 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git tags/for-net-next-2025-05-21
> > >
> > > for you to fetch changes up to 623029dcc53837d409deb70b65eb7c7b83ab9b9a:
> > >
> > > Bluetooth: MGMT: iterate over mesh commands in mgmt_mesh_foreach() (2025-05-21 10:31:01 -0400)
> >
> > Another bad fixes tag :( Time to automate this on your side?
> >
> > Commit: ee1d8d65dffd ("Bluetooth: L2CAP: Fix not checking l2cap_chan security level")
> > Fixes tag: Fixes: 50c1241e6a8a ("Bluetooth: l2cap: Check encryption key size on incoming connection")
> > Has these problem(s):
> > - Target SHA1 does not exist
> > --
> > pw-bot: cr
>
> Will fix it, didn't we apply it to net already though? Seems like
> net-next doesn't have it yet.
I see, that's an extra complication, indeed.
I have net merged in locally, just waiting for builds to finish
before pushing. The commit in downstream trees has a different hash:
522e9ed157e3 ("Bluetooth: l2cap: Check encryption key size on incoming connection")
