From: Vinod Koul <vinod.koul@intel.com>
To: Guneshwor Singh <guneshwor.o.singh@intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
ALSA <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Patches Audio <patches.audio@intel.com>
Subject: Re: [PATCH] ASoC: hdac_hdmi: Add vendor id for Cannonlake HDMI codec
Date: Thu, 21 Dec 2017 09:56:00 +0530 [thread overview]
Message-ID: <20171221042600.GL18649@localhost> (raw)
In-Reply-To: <20171221031529.14234-1-guneshwor.o.singh@intel.com>
On Thu, Dec 21, 2017 at 08:45:29AM +0530, Guneshwor Singh wrote:
> Cannonlake HDMI codec has the same nid as Geminilake. This adds the
> vendor id for Cannonlake in hdmi device id list.
Acked-By: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
next prev parent reply other threads:[~2017-12-21 4:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 3:15 [PATCH] ASoC: hdac_hdmi: Add vendor id for Cannonlake HDMI codec Guneshwor Singh
2017-12-21 4:26 ` Vinod Koul [this message]
2017-12-21 12:44 ` Applied "ASoC: hdac_hdmi: Add vendor id for Cannonlake HDMI codec" to the asoc tree 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=20171221042600.GL18649@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guneshwor.o.singh@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@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