From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] regulator: fixed: Remove WARs for handling of_get_named_gpio() return
Date: Sun, 13 Mar 2016 18:25:03 +0530 [thread overview]
Message-ID: <56E56327.9040908@nvidia.com> (raw)
In-Reply-To: <20160312055814.GU3898@sirena.org.uk>
On Saturday 12 March 2016 11:28 AM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> 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.
OK, will send the patch with term "workaround".
prev parent reply other threads:[~2016-03-13 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 12:12 [PATCH] regulator: fixed: Remove WARs for handling of_get_named_gpio() return Laxman Dewangan
2016-03-10 12:12 ` [PATCH] regulator: of: Use of_property_read_u32() for reading min/max Laxman Dewangan
2016-03-11 4:30 ` [PATCH] regulator: fixed: Remove WARs for handling of_get_named_gpio() return Mark Brown
2016-03-11 8:14 ` Laxman Dewangan
2016-03-12 5:58 ` Mark Brown
2016-03-13 12:55 ` Laxman Dewangan [this message]
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=56E56327.9040908@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.