From: Mark Brown <broonie@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>,
patches@opensource.cirrus.com, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: WM8962 crashing on suspend
Date: Thu, 28 Apr 2022 13:45:40 +0100 [thread overview]
Message-ID: <YmqMdMNu2258MO9b@sirena.org.uk> (raw)
In-Reply-To: <CAHCN7xKOr5CJbBCCxJTUoyDndRy0rkfgk-N1WKJ5iAZsdTXS2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Thu, Apr 28, 2022 at 07:21:39AM -0500, Adam Ford wrote:
> On Thu, Apr 28, 2022 at 3:23 AM Charles Keepax
> > Nah, its good your ok to upstream your out of tree patch, just
> > making sure I fill in the holes in my knowledge with Mark :-)
> I'd like to push the patch with a Fixes tag, but I am not sure that we
> have a definitive hash to use. Ideally, it'd get backported, but I am
> not sure that I have the means to test it, because the hardware
> platform I have doesn't go back that far. Any thoughts? If not, I'll
> just push it without a fixes tag.
Cc stable does just as well, though TBH just having the word "fix"
somewhere in the changelog will probably cause the bots to pick it up.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-04-28 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 16:36 WM8962 crashing on suspend Adam Ford
2022-04-26 17:32 ` Mark Brown
2022-04-26 17:41 ` Charles Keepax
2022-04-27 13:12 ` Adam Ford
2022-04-27 13:21 ` Mark Brown
2022-04-27 14:58 ` Charles Keepax
2022-04-27 14:57 ` Charles Keepax
2022-04-27 15:24 ` Mark Brown
2022-04-27 16:48 ` Charles Keepax
2022-04-27 16:54 ` Adam Ford
2022-04-28 8:23 ` Charles Keepax
2022-04-28 12:21 ` Adam Ford
2022-04-28 12:45 ` Mark Brown [this message]
2022-04-27 17:02 ` Mark Brown
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=YmqMdMNu2258MO9b@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aford173@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.cirrus.com \
--cc=tiwai@suse.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox