From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, bardliao@realtek.com, alsa-devel@alsa-project.org,
broonie@kernel.org
Subject: Re: [PATCH 0/3] Intel-rt5670 updates
Date: Fri, 8 Sep 2017 09:38:11 +0530 [thread overview]
Message-ID: <20170908040811.GA3053@localhost> (raw)
In-Reply-To: <20170908011256.7706-1-pierre-louis.bossart@linux.intel.com>
On Thu, Sep 07, 2017 at 08:12:53PM -0500, Pierre-Louis Bossart wrote:
> Instead of submitting all my patches at ones, I broke them by
> platforms/codecs. This series is only for Intel-rt5670 platforms. It
> fixes a mistake on the Dell Venue 5585 - corrected with the help from
> Realtek and Dell who kindly provided schematics and data sheet
> information needed to fix non-working DMIC capture. Since there are
> still some reports of non-functional audio on some platforms, I added
> quirks that can be changed from the kernel command line (and later
> added as DMI-based quirks). The last two patches are minor corrections
> to fix ACPI HID naming issues and use a more meaningful card name.
>
> Pierre-Louis Bossart (3):
> ASoC: rt5670: refactor DMI quirks and fix Dell Venue settings
> ASoC: Intel: cht_bsw_rt5672: use actual HID in suspend/resume
> ASoC: Intel: cht_bsw_rt5672: fix card name
The last two:
Acked-By: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
prev parent reply other threads:[~2017-09-08 4:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 1:12 [PATCH 0/3] Intel-rt5670 updates Pierre-Louis Bossart
2017-09-08 1:12 ` [PATCH 1/3] ASoC: rt5670: refactor DMI quirks and fix Dell Venue settings Pierre-Louis Bossart
2017-09-08 8:12 ` Takashi Iwai
2017-09-25 16:16 ` Applied "ASoC: rt5670: refactor DMI quirks and fix Dell Venue settings" to the asoc tree Mark Brown
2017-09-08 1:12 ` [PATCH 2/3] ASoC: Intel: cht_bsw_rt5672: use actual HID in suspend/resume Pierre-Louis Bossart
2017-09-08 1:12 ` [PATCH 3/3] ASoC: Intel: cht_bsw_rt5672: fix card name Pierre-Louis Bossart
2017-09-08 8:16 ` Takashi Iwai
2017-09-08 4:08 ` Vinod Koul [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=20170908040811.GA3053@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).