Comment 13 for bug 2042902

I got a ping on patch pilot duty, sadly on my ping back if they would be
available for questions if I find more that needs to be sorted out was
unanswered. So I need to carry all into this bug.

This is kind of a log of my own understanding process, feel free to ignore it:
Proposed change:
- It adds a few regex expressions to allow matching the new HW
- and then configuration for those new matches
- Accepted upstream
- Other than fixup releases Upstream seems to tag two releases per year, one in Q2 one in Q4
  - Due to that I'd this to be in a new revision v1.2.11 by May 2024
  - that might be worth to mention for packages to know when they will be able to drop it

Paride and Athos guided you to correctly obey the usual "fix -devel first" rule
and due to noble being new that you need to start there.

We are adding one particular device, but I see that due to having added
Ubuntu delta in the past we have not yet picked up 1.2.10 which would have
picked up plenty of other fixes and devices.
=> https://github.com/alsa-project/alsa-ucm-conf/releases/tag/v1.2.10

alsa-ucm-conf | 1.2.10-1 | unstable | source, all
alsa-ucm-conf | 1.2.9-1ubuntu3 | noble | source, all

The SRU fix is fine, those are meant to be surgical based on the need of our
users, but for noble it feels we should aim for 1.2.10 + this.
Checking who usually did that, ah Jürg and Ethan - fine we can ask them
for opinions as they might know the subject matter.

Great, so I'd propose we combine a merge of 1.2.10 with your fix on top.