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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 28 Apr 2020 18:27:45 +0000
From:   Leslie Hsia(夏邦進_Pegatron) 
        <Leslie_Hsia@...atroncorp.com>
To:     Mark Brown <broonie@...nel.org>
CC:     "knaack.h@....de" <knaack.h@....de>,
        "lars@...afoo.de" <lars@...afoo.de>,
        "pmeerw@...erw.net" <pmeerw@...erw.net>,
        "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Hermes Hsieh(謝旻劭_Pegatron) 
        <Hermes_Hsieh@...atroncorp.com>,
        "jesse.sung@...onical.com" <jesse.sung@...onical.com>,
        "jic23@...nel.org" <jic23@...nel.org>
Subject: Re: [PATCH] subsystem: Amplifier driver for TAS5805M,Texas
 instruments

Hi Mark,

Yes, I agree that the code didn’t integrate with ALSA API,
and we only need to initialize i2c registers due to make the amplifier works properly,
and I do find there is already an amplifier driver in /drivers/iio/amplifier/,
that’s why I sent the patch to Jonathan,
I want to put this driver into /drivers/iio/amplifier/,
but he thought that this is an amplifier driver,
and we should put it into /sound/doc/codecs/,
so would you please give me an advice about the driver belongs to which subsystem?
Jonathan, what do you think?

Best Regards,
Leslie

> Mark Brown <broonie@...nel.org> 於 2020年4月28日 下午7:30 寫道:
>
> On Tue, Apr 28, 2020 at 10:43:18AM +0000, Leslie Hsia(夏邦進_Pegatron) wrote:
>> *   Author: Leslie Hsia
>> *   Amplifier driver for TAS5805M, initial the amplifier and set the sound parameter.
>> *   Signed-off-by: Leslie Hsia <Leslie_Hsia@...atroncorp.com<mailto:Leslie_Hsia@...atroncorp.com>>
>
> Please follow the patch submission process that is described in
> Documentation/process/submitting-patches.rst in the kernel source.  Take
> a look at other submissions on the list and follow a similar process.
> There also appear to be both IIO and ASoC drivers in there which is at
> best a bit weird.
>
> Having done a quick scan through your code it doesn't actually seem to
> integrate with the subsystem at all (there's no
> snd_soc_register_codec())
>
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.


This e-mail and its attachment may contain information that is confidential or privileged, and are solely for the use of the individual to whom this e-mail is addressed. If you are not the intended recipient or have received it accidentally, please immediately notify the sender by reply e-mail and destroy all copies of this email and its attachment. Please be advised that any unauthorized use, disclosure, distribution or copying of this email or its attachment is strictly prohibited.

本電子郵件及其附件可能含有機密或依法受特殊管制之資訊,僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件,請立即回覆郵件通知寄件人,並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為,皆嚴格禁止 。

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ