From: Vinod Koul <vinod.koul@intel.com>
To: Kevin Cheng <kevin.cheng@intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 0/2] ASoC: Intel: Add Kabylake machine driver for RT5663
Date: Thu, 27 Jul 2017 13:50:29 +0530 [thread overview]
Message-ID: <20170727082029.GO3053@localhost> (raw)
In-Reply-To: <20170727025400.6426-1-kevin.cheng@intel.com>
On Thu, Jul 27, 2017 at 10:53:58AM +0800, Kevin Cheng wrote:
> Add kabylake machine driver & corresponding driver entry in machine table for
> rt5663 codec.
>
> For this particular machine,
> the RT5663 is a headset codec connected on ssp1.
> there is no dmic and speaker connected.
>
> Modify the machine driver in kbl_rt5663_max98927 to reuse the
> common codes.
Hello Kevin,
The patch series looks good to me, but will unfortunately get ignored as you
have not CCed maintainers.
Please resend it and CC Takash and Mark
>
> V2: adjust the code order.
>
> Kevin Cheng (2):
> ASoC: Intel: Add Kabylake machine driver for RT5663
> ASoC: Intel: Add Kabylake RT5663 machine driver entry
>
> sound/soc/intel/boards/kbl_rt5663_max98927.c | 246 +++++++++++++++++++++++----
> sound/soc/intel/skylake/skl.c | 5 +
> 2 files changed, 214 insertions(+), 37 deletions(-)
>
> --
> 2.12.2
>
--
~Vinod
next prev parent reply other threads:[~2017-07-27 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 2:53 [PATCH v2 0/2] ASoC: Intel: Add Kabylake machine driver for RT5663 Kevin Cheng
2017-07-27 2:53 ` [PATCH v2 1/2] " Kevin Cheng
2017-07-28 12:37 ` Applied "ASoC: Intel: Add Kabylake machine driver for RT5663" to the asoc tree Mark Brown
2017-07-27 2:54 ` [PATCH v2 2/2] ASoC: Intel: Add Kabylake RT5663 machine driver entry Kevin Cheng
2017-07-27 8:20 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-27 8:38 [PATCH v2 0/2] ASoC: Intel: Add Kabylake machine driver for RT5663 Kevin Cheng
2017-07-28 3:21 ` Vinod Koul
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=20170727082029.GO3053@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=kevin.cheng@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.