From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
alsa-devel@alsa-project.org, Jie Yang <yang.jie@linux.intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v1] ASoC: Intel: catpt: Replace open coded variant of resource_intersection()
Date: Wed, 2 Dec 2020 12:28:26 +0000 [thread overview]
Message-ID: <20201202122826.GB5560@sirena.org.uk> (raw)
In-Reply-To: <20201201183329.GI4077@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
On Tue, Dec 01, 2020 at 08:33:29PM +0200, Andy Shevchenko wrote:
> As I mentioned in the comment (after --- line) the patch relies on the stuff in
> linux-pm tree. Do you have any immutable branch pulled? Otherwise Rafael
> already took it where it won't break compilation.
b4 had a bug which caused it to send thanks for every patch I'd ever
downloaded but not applied, the "no commit info" means there wasn't an
actual matching commit. I'd been going to review it but then it got
applied anyway.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-12-02 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 9:56 [PATCH v1] ASoC: Intel: catpt: Replace open coded variant of resource_intersection() Andy Shevchenko
2020-11-24 12:13 ` Rojewski, Cezary
2020-11-25 15:49 ` Rafael J. Wysocki
2020-11-25 16:10 ` Andy Shevchenko
2020-11-25 16:10 ` Rafael J. Wysocki
2020-11-25 16:18 ` Andy Shevchenko
2020-12-01 13:57 ` Mark Brown
2020-12-01 18:33 ` Andy Shevchenko
2020-12-02 12:28 ` Mark Brown [this message]
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=20201202122826.GB5560@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=cezary.rojewski@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=yang.jie@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