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]
Message-ID: <20160312055814.GU3898@sirena.org.uk>
Date:	Sat, 12 Mar 2016 12:58:14 +0700
From:	Mark Brown <broonie@...nel.org>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	lgirdwood@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: fixed: Remove WARs for handling
 of_get_named_gpio() return

On Fri, Mar 11, 2016 at 01:44:18PM +0530, Laxman Dewangan wrote:
> On Friday 11 March 2016 10:00 AM, Mark Brown wrote:

> >>Remove the WAR implemented in fixed regulator to handle the
> >>return of of_get_named_gpio().

> >You need to explain what a WAR is, I suspect it's some nVidia internal
> >term.

> We used term "WAR" as workaround. This we used for special handling in SW
> for unusual stuff.
> Probably "Hack" is the more appropriate word.

> Should I use "hack" here?

What is wrong with "workaround"?  Or just generally write the commit
message so someone outside nVidia can tell what the commit message
means.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ