From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, broonie@kernel.org,
peter.ujfalusi@linux.intel.com,
ranjani.sridharan@linux.intel.com
Subject: Re: [PATCH 3/3] ASoC: SOF: Intel: disable IMR boot when resuming from ACPI S4 and S5 states
Date: Mon, 25 Jul 2022 10:25:07 -0500 [thread overview]
Message-ID: <56549c69-39a1-56cf-fb48-e2af6eeadef5@linux.intel.com> (raw)
In-Reply-To: <Ytv9JKlEOXctrFee@kroah.com>
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?
Thanks
-Pierre
next prev parent reply other threads:[~2022-07-25 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 15:57 [PATCH 0/3] [5.18.y backport] ASoC: SOF: Intel: fix resume from hibernate Pierre-Louis Bossart
2022-07-11 15:57 ` [PATCH 1/3] ASoC: SOF: pm: add explicit behavior for ACPI S1 and S2 Pierre-Louis Bossart
2022-07-23 13:51 ` Greg KH
2022-07-11 15:57 ` [PATCH 2/3] ASoC: SOF: pm: add definitions for S4 and S5 states Pierre-Louis Bossart
2022-07-23 13:52 ` Greg KH
2022-07-11 15:57 ` [PATCH 3/3] ASoC: SOF: Intel: disable IMR boot when resuming from ACPI " Pierre-Louis Bossart
2022-07-23 13:52 ` Greg KH
2022-07-25 15:25 ` Pierre-Louis Bossart [this message]
2022-07-25 17:36 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-06-16 20:18 [PATCH 0/3] ASoC: SOF: Intel: fix resume from hibernate Pierre-Louis Bossart
2022-06-16 20:18 ` [PATCH 3/3] ASoC: SOF: Intel: disable IMR boot when resuming from ACPI S4 and S5 states Pierre-Louis Bossart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56549c69-39a1-56cf-fb48-e2af6eeadef5@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.