From: Takashi Iwai <tiwai@suse.de>
To: Stefan Binding <sbinding@opensource.cirrus.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
patches@opensource.cirrus.com, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v2] ALSA: hda: cs35l41: Clarify support for CSC3551 without _DSD Properties
Date: Tue, 16 Aug 2022 15:13:16 +0200 [thread overview]
Message-ID: <87mtc4xrf7.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220815162906.463108-1-sbinding@opensource.cirrus.com>
On Mon, 15 Aug 2022 18:29:06 +0200,
Stefan Binding wrote:
>
> For devices which use HID CSC3551, correct ACPI _DSD properties are
> required to be able support those systems.
> Add error message to clarify this.
>
> Signed-off-by: Stefan Binding <sbinding@opensource.cirrus.com>
Thanks, applied.
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Stefan Binding <sbinding@opensource.cirrus.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH v2] ALSA: hda: cs35l41: Clarify support for CSC3551 without _DSD Properties
Date: Tue, 16 Aug 2022 15:13:16 +0200 [thread overview]
Message-ID: <87mtc4xrf7.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220815162906.463108-1-sbinding@opensource.cirrus.com>
On Mon, 15 Aug 2022 18:29:06 +0200,
Stefan Binding wrote:
>
> For devices which use HID CSC3551, correct ACPI _DSD properties are
> required to be able support those systems.
> Add error message to clarify this.
>
> Signed-off-by: Stefan Binding <sbinding@opensource.cirrus.com>
Thanks, applied.
Takashi
next prev parent reply other threads:[~2022-08-16 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 16:29 [PATCH v2] ALSA: hda: cs35l41: Clarify support for CSC3551 without _DSD Properties Stefan Binding
2022-08-15 16:29 ` Stefan Binding
2022-08-16 13:13 ` Takashi Iwai [this message]
2022-08-16 13:13 ` 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=87mtc4xrf7.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=sbinding@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.