From: Takashi Iwai <tiwai@suse.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Shenghao Ding <shenghao-ding@ti.com>,
robh+dt@kernel.org, lgirdwood@gmail.com, perex@perex.cz,
kevin-lu@ti.com, 13916275206@139.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
liam.r.girdwood@intel.com, mengdong.lin@intel.com,
baojun.xu@ti.com, thomas.gfeller@q-drop.com, peeyush@ti.com,
navada@ti.com, broonie@kernel.org, gentuser@gmail.com
Subject: Re: [PATCH v4 1/2] ALSA: hda/tas2781: Add tas2781 HDA driver
Date: Fri, 18 Aug 2023 19:32:43 +0200 [thread overview]
Message-ID: <87r0o0gssk.wl-tiwai@suse.de> (raw)
In-Reply-To: <72960354-3f69-e2fa-e7b0-dc8b61ca4940@linux.intel.com>
On Fri, 18 Aug 2023 18:36:16 +0200,
Pierre-Louis Bossart wrote:
>
>
>
> On 8/18/23 05:17, Takashi Iwai wrote:
> > On Fri, 18 Aug 2023 10:58:35 +0200,
> > Shenghao Ding wrote:
> >>
> >> Integrate tas2781 configs for Lenovo Laptops. All of the tas2781s in the
> >> laptop will be aggregated as one audio device. The code support realtek
> >> as the primary codec. Rename "struct cs35l41_dev_name" to
> >> "struct scodec_dev_name" for all other side codecs instead of the certain
> >> one.
> >>
> >> Signed-off-by: Shenghao Ding <shenghao-ding@ti.com>
> >
> > Now I applied both patches to for-next branch.
> >
> > The patch 2 needed some minor adjustment in Kconfig to be applied to
> > the latest branch, but I resolved it locally.
>
> There are a number of issues I just reported, I guess they will have to
> be handled with a follow-up patch now?
Yes, let's fix incrementally on the top.
Takashi
next prev parent reply other threads:[~2023-08-18 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 8:58 [PATCH v4 1/2] ALSA: hda/tas2781: Add tas2781 HDA driver Shenghao Ding
2023-08-18 8:58 ` [PATCH v4 2/2] " Shenghao Ding
2023-08-18 10:17 ` [PATCH v4 1/2] " Takashi Iwai
2023-08-18 16:36 ` Pierre-Louis Bossart
2023-08-18 17:32 ` Takashi Iwai [this message]
2023-08-18 18:28 ` Takashi Iwai
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=87r0o0gssk.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=13916275206@139.com \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=broonie@kernel.org \
--cc=gentuser@gmail.com \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=navada@ti.com \
--cc=peeyush@ti.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=shenghao-ding@ti.com \
--cc=thomas.gfeller@q-drop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox