lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 18 Aug 2023 20:28:36 +0200
From:   Takashi Iwai <tiwai@...e.de>
To:     Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc:     Shenghao Ding <shenghao-ding@...com>, robh+dt@...nel.org,
        lgirdwood@...il.com, perex@...ex.cz, kevin-lu@...com,
        13916275206@....com, alsa-devel@...a-project.org,
        linux-kernel@...r.kernel.org, liam.r.girdwood@...el.com,
        mengdong.lin@...el.com, baojun.xu@...com,
        thomas.gfeller@...rop.com, peeyush@...com, navada@...com,
        broonie@...nel.org, gentuser@...il.com
Subject: Re: [PATCH v4 1/2] ALSA: hda/tas2781: Add tas2781 HDA driver

On Fri, 18 Aug 2023 19:32:43 +0200,
Takashi Iwai wrote:
> 
> 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@...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.

... and since it's already merged, it means that everyone can submit
patches for fixing issues there, and I'd happily apply fixes no matter
who submitted them, as long as the fixes are correct ;)


Takashi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ