From: Cezary Rojewski <cezary.rojewski@intel.com>
To: <broonie@kernel.org>, Takashi Iwai <tiwai@suse.com>
Cc: <alsa-devel@alsa-project.org>, <linux-sound@vger.kernel.org>,
<perex@perex.cz>, <amadeuszx.slawinski@linux.intel.com>,
<pierre-louis.bossart@linux.intel.com>, <hdegoede@redhat.com>,
<rafael@kernel.org>
Subject: Re: [PATCH 1/2] ALSA: hda: intel-dsp-config: Switch to ACPI NHLT
Date: Thu, 9 May 2024 13:15:15 +0200 [thread overview]
Message-ID: <892ad456-cfe5-4ff1-ab67-7709677608cd@intel.com> (raw)
In-Reply-To: <20240419084307.2718881-2-cezary.rojewski@intel.com>
On 2024-04-19 10:43 AM, Cezary Rojewski wrote:
> From: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
>
> Now that NHLT support in ACPI framework was introduced, migrate
> intel-dsp-config driver to new API.
Hello,
I see that this patch has not landed in Mark's for-next. Takashi, what's
the verdict here? Should this go entirely (entire patchset) through Mark
or should the NHLT changes [1] plus this patch alone be incorporated
into for-next of yours separately?
[1]:
https://lore.kernel.org/linux-acpi/20240319083018.3159716-1-cezary.rojewski@intel.com/
Kind regards,
Czarek
next prev parent reply other threads:[~2024-05-09 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 8:43 [PATCH 0/2] ASoC: Intel: avs: Switch to acpi-nhlt Cezary Rojewski
2024-04-19 8:43 ` [PATCH 1/2] ALSA: hda: intel-dsp-config: Switch to ACPI NHLT Cezary Rojewski
2024-05-09 11:15 ` Cezary Rojewski [this message]
2024-05-09 12:35 ` Takashi Iwai
2024-05-09 13:08 ` Takashi Iwai
2024-05-09 15:41 ` Mark Brown
2024-05-09 18:25 ` Takashi Iwai
2024-04-19 8:43 ` [PATCH 2/2] ASoC: Intel: avs: " Cezary Rojewski
2024-04-22 8:09 ` (subset) [PATCH 0/2] ASoC: Intel: avs: Switch to acpi-nhlt 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=892ad456-cfe5-4ff1-ab67-7709677608cd@intel.com \
--to=cezary.rojewski@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rafael@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