From: Mark Brown <broonie@kernel.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: fixed: Remove WARs for handling of_get_named_gpio() return
Date: Sat, 12 Mar 2016 12:58:14 +0700 [thread overview]
Message-ID: <20160312055814.GU3898@sirena.org.uk> (raw)
In-Reply-To: <56E27E5A.7040705@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-13 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 12:12 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 [this message]
2016-03-13 12:55 ` Laxman Dewangan
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=20160312055814.GU3898@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ldewangan@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®