From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Gaosheng Cui <cuigaosheng1@huawei.com>,
cezary.rojewski@intel.com, tiwai@suse.com,
ranjani.sridharan@linux.intel.com,
pierre-louis.bossart@linux.intel.com, perex@perex.cz,
liam.r.girdwood@linux.intel.com, kai.vehmanen@linux.intel.com,
peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] ASoC: Intel: fix unused-variable warning in probe_codec
Date: Wed, 14 Sep 2022 11:31:23 +0100 [thread overview]
Message-ID: <YyGte0fkdquTxLC4@sirena.org.uk> (raw)
In-Reply-To: <87zgf2tfn3.wl-tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
On Wed, Sep 14, 2022 at 12:27:28PM +0200, Takashi Iwai wrote:
> Mark Brown wrote:
> > [1/1] ASoC: Intel: fix unused-variable warning in probe_codec
> > commit: 515626a33a194c4caaf2879dbf9e00e882582af0
> I thought the buggy commit 3fd63658caed9 was present only in my tree
> for now, but if it's in your tree, that's fine to apply through
> yours. Then I'll drop from mine.
Huh, right - I think you're right here and it is only in your
tree, it just didn't trigger any issues in my coverage tests
prior to merge. Probably best to leave it in your tree and
either have a double apply or I'll revert it from mine. Either
way it'll get fixed by the time it gets sent to Linus.
I'd not remembered that you had any extra stuff for ASoC in your
tree, sorry.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-09-14 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 3:51 [PATCH -next] ASoC: Intel: fix unused-variable warning in probe_codec Gaosheng Cui
2022-09-13 14:03 ` Cezary Rojewski
2022-09-13 15:21 ` Takashi Iwai
2022-09-14 9:40 ` Mark Brown
2022-09-14 10:27 ` Takashi Iwai
2022-09-14 10:31 ` Mark Brown [this message]
2022-09-14 10:43 ` Takashi Iwai
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=YyGte0fkdquTxLC4@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=cuigaosheng1@huawei.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=yung-chuan.liao@linux.intel.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