From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Nikhil Mahale <nmahale@nvidia.com>,
tiwai@suse.com, alsa-devel@alsa-project.org,
aplattner@nvidia.com
Subject: Re: [alsa-devel] [PATCH v3 0/4] ALSA: hda - Add DP-MST support for NVIDIA codecs
Date: Tue, 19 Nov 2019 15:40:34 +0200 (EET) [thread overview]
Message-ID: <alpine.DEB.2.21.1911191539040.16459@zeliteleevi> (raw)
In-Reply-To: <s5hftikcewy.wl-tiwai@suse.de>
Hi Takashi and Nikhil,
On Tue, 19 Nov 2019, Takashi Iwai wrote:
> OK, you've done in time for 5.5 :)
> Now applied all four patches.
>
> Kai, please let me know if the intel CI catches any issue with these
> changes.
tests just completed and no issues found so seem good to go.
Br, Kai
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2019-11-19 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 8:47 [alsa-devel] [PATCH v3 0/4] ALSA: hda - Add DP-MST support for NVIDIA codecs Nikhil Mahale
2019-11-19 8:47 ` [alsa-devel] [PATCH v3 1/4] ALSA: hda - Rename snd_hda_pin_sense to snd_hda_jack_pin_sense Nikhil Mahale
2019-11-19 8:47 ` [alsa-devel] [PATCH v3 2/4] ALSA: hda - Add DP-MST jack support Nikhil Mahale
2019-11-19 8:47 ` [alsa-devel] [PATCH v3 3/4] ALSA: hda - Add DP-MST support for non-acomp codecs Nikhil Mahale
2019-11-19 8:47 ` [alsa-devel] [PATCH v3 4/4] ALSA: hda - Add DP-MST support for NVIDIA codecs Nikhil Mahale
2020-02-01 15:28 ` Martin Regner
2020-02-02 8:37 ` Takashi Iwai
2020-02-02 14:18 ` Martin Regner
2020-02-02 23:00 ` Jaroslav Kysela
2020-02-02 23:50 ` Martin Regner
2020-02-03 7:37 ` Jaroslav Kysela
2020-02-03 9:14 ` Nikhil Mahale
2019-11-19 10:57 ` [alsa-devel] [PATCH v3 0/4] " Takashi Iwai
2019-11-19 13:40 ` Kai Vehmanen [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=alpine.DEB.2.21.1911191539040.16459@zeliteleevi \
--to=kai.vehmanen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=aplattner@nvidia.com \
--cc=nmahale@nvidia.com \
--cc=tiwai@suse.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).