#asahi-dev · 2024-05-10 18:41
john-cabajjannau: When new release tags are made, I notice previous commits have changed history - not necessarily content, but the commit dates. Do commits from previous release tags get updated frequently enough that it would be better to always update every Asahi patch for each Ubuntu Asahi release, or is it safe to just find the new commits with different commit messages and assume those are new, and the old commits are s#asahi-dev · 2023-11-28 21:02
john-cabajYeah, could do that too. Then will need backport kernels to previous releases. But that still might be easier.#asahi-dev · 2023-11-28 21:00
john-cabajThanks#asahi-dev · 2023-11-28 20:59
john-cabajGood idea, that's a start.#asahi-dev · 2023-11-28 20:56
john-cabajBut those weren't Asahi specific. Anything Asahi specific existing upstream in 6.6 not in 6.5 is a bit of a blind spot.#asahi-dev · 2023-11-28 20:56
john-cabajThere's definitely iommu changes between 6.5 and 6.6 that some Asahi patches will need backported, possibly others.#asahi-dev · 2023-11-28 20:50
john-cabajCorrect#asahi-dev · 2023-11-28 20:21
john-cabajApologies if this has been discussed, but have any Asahi patches been upstreamed in 6.6 not in 6.5? It's easy enough to backport Asahi commits following the v6.6 tag, but if any patches fell in 6.6, it's trickier to determine.