From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: stable@vger.kernel.org, Oder Chiou <oder_chiou@realtek.com>,
Bard Liao <bardliao@realtek.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Brian Norris <briannorris@chromium.org>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: Applied "ASoC: rt5514-spi: Check the validity of drvdata pointer on resume" to the asoc tree
Date: Wed, 24 Jan 2018 15:47:35 +0000 [thread overview]
Message-ID: <20180124154735.GG9366@sirena.org.uk> (raw)
In-Reply-To: <E1eeN5q-0004lO-5c@debutante>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On Wed, Jan 24, 2018 at 03:36:06PM +0000, Mark Brown wrote:
> The patch
>
> ASoC: rt5514-spi: Check the validity of drvdata pointer on resume
>
> has been applied to the asoc tree at
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
Dropped again - this was fixed with "ASoC: rt5514-spi: only enable wakeup
when fully initialized" which was already in Linus' tree. Dunno if that
was part of why it went AWOL, I wouldn't have thought so as I usually
send a "this didn't apply" mail. No idea what happened.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-01-24 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 1:12 [PATCH for-4.15] ASoC: rt5514: don't assume rt5514 component was "attached" Brian Norris
2017-12-16 3:17 ` Brian Norris
[not found] ` <CAFv8Nw+qiWedqZeVsPn17WiSyc_zwOP3bEnxn2Wc-oQ3ntgq2g@mail.gmail.com>
2017-12-18 17:42 ` Brian Norris
2017-12-19 7:38 ` Cheng-yi Chiang
2017-12-19 10:58 ` Mark Brown
2017-12-19 17:31 ` Brian Norris
2018-01-24 15:36 ` Applied "ASoC: rt5514-spi: Check the validity of drvdata pointer on resume" to the asoc tree Mark Brown
2018-01-24 15:47 ` Mark Brown [this message]
2018-01-24 17:07 ` Brian Norris
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=20180124154735.GG9366@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=briannorris@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=oder_chiou@realtek.com \
--cc=stable@vger.kernel.org \
--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
Powered by JetHome