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]
Message-ID: <00FC9A978A94B7418C33AFAE8A35ED49D80BB3@DFLE09.ent.ti.com>
Date:	Mon, 14 Jul 2014 19:33:35 +0000
From:	"Murphy, Dan" <dmurphy@...com>
To:	Mark Brown <broonie@...nel.org>
CC:	"linux-sound@...r.kernel.org" <linux-sound@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v6] ASoC: tas2552: Support TI TAS2552 Amplifier

Mark

On 07/14/2014 02:17 PM, Mark Brown wrote:
> On Mon, Jul 14, 2014 at 07:07:06PM +0000, Murphy, Dan wrote:
>> On 07/14/2014 01:43 PM, Mark Brown wrote:
>>>> +config SND_SOC_TAS2552
>>>> +	tristate "Texas Instruments TAS2552 Mono Audio amplifier"
>>>> +	depends on I2C
>>>> +
>>>>  endmenu
>>> Keep this and Makefile sorted - since this is a proper CODEC driver it
>>> should be in with the CODECs and also sorted in alphabetical order.
>> OK.  I was trying to stay away from a conflict by adding to the
>> bottom of the file.
> The whole point is to avoid conflicts - if everyone adds at the bottom
> of the file any two adds are pretty much guaranteed to conflict either
> on application or on merge.  Sorting avoids most of these and makes any
> that do occur much clearer.

No worries I will fix it

-- 
------------------
Dan Murphy

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ