From: Jaroslav Kysela <perex@perex.cz>
To: Hans de Goede <hdegoede@redhat.com>
Cc: alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Bard Liao <bard.liao@intel.com>
Subject: Re: [PATCH alsa-ucm-conf 0/5] bytcr-rt5640: Fixes and improvements
Date: Wed, 29 Sep 2021 12:58:40 +0200 [thread overview]
Message-ID: <23bff35b-71ab-1f8c-c03f-664ec051f194@perex.cz> (raw)
In-Reply-To: <20210929091144.4778-1-hdegoede@redhat.com>
On 29. 09. 21 11:11, Hans de Goede wrote:
> Hi Jaroslav,
>
> Here is a patch series with 2 bug-fixes for X86 devices with a rt5640
> codec (these 2 are a resend) + 3 patches adding support for the second
> headset-jack (on the dock) found on the HP elitepad 1000 G2.
>
> The new kernel-bits for the second headset-jack have already landed,
> so this is ready for merging.
Thank you for this update and your work. I applied all patches to the
alsa-ucm-conf repo.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
prev parent reply other threads:[~2021-09-29 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 9:11 [PATCH alsa-ucm-conf 0/5] bytcr-rt5640: Fixes and improvements Hans de Goede
2021-09-29 9:11 ` [PATCH alsa-ucm-conf 1/5] bytcr-rt5640: Fix 'Headphone Switch' / 'Headset Mic Switch' no longer getting set Hans de Goede
2021-09-29 9:11 ` [PATCH alsa-ucm-conf 2/5] codecs/rt5640: Rename DAPM PIN switches to avoid having 2 Speaker and Headphones switches Hans de Goede
2021-09-29 9:11 ` [PATCH alsa-ucm-conf 3/5] bytcr-rt5640: Add support for devices using the DMIC2 input for their internal mic(s) Hans de Goede
2021-09-29 9:11 ` [PATCH alsa-ucm-conf 4/5] bytcr-rt5640: Add support for a second headphones output Hans de Goede
2021-09-29 9:11 ` [PATCH alsa-ucm-conf 5/5] bytcr-rt5640: Add support for a second headset input Hans de Goede
2021-09-29 10:58 ` Jaroslav Kysela [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=23bff35b-71ab-1f8c-c03f-664ec051f194@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=hdegoede@redhat.com \
--cc=pierre-louis.bossart@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 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.