On Mon, Jul 25, 2022 at 10:25:07AM -0500, Pierre-Louis Bossart wrote: > > > On 7/23/22 08:52, Greg KH wrote: > > On Mon, Jul 11, 2022 at 10:57:19AM -0500, Pierre-Louis Bossart wrote: > >> commit 58ecb11eab44dd5d64e35664ac4d62fecb6328f4 upstream. > > > > Again, not a valid commit :( > > > > Where did these come from? > > > > confused, > > There are on Mark Brown's for-next branch, I must have looked at the IDs > after a rebase or something. We always report the SHA IDs from that > for-next branch, and linux-next check those values. I didn't realize > they could be different in Linus' tree. > > I am still a bit confused since our Fixes tag could be right at the > moment we submit the patches to Mark but wrong long-term after merge by > Linus. Either I need more coffee, or I am missing a key concept, or both. > > The commit IDs on Linus' tree should be: > > a933084558c6 ASoC: SOF: pm: add explicit behavior for ACPI S1 and S2 > > 9d2d46271338 ASoC: SOF: pm: add definitions for S4 and S5 states > > 391153522d18 ASoC: SOF: Intel: disable IMR boot when resuming from ACPI > S4 and S5 states > > > Do you want me to resend? Yes please.
