The point for me is that we should be trying to avoid taking on indefinite technical debt (patches that have to be rebased forever). It's "fine" to include them ahead of any upstream schedule if we need to for hardware enablement, but we do need to have plans to make this be a non permanent situation. That's what Seb is asking for, and I'm totally on board with that.
btw, I don't think it's fair to characterise code review as pedantry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
