From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Andrew Morton'" <akpm@linux-foundation.org>,
"'Guennadi Liakhovetski'" <g.liakhovetski@gmx.de>,
linux-kernel@vger.kernel.org,
"'Magnus Damm'" <magnus.damm@gmail.com>,
"'Simon Horman'" <horms@verge.net.au>,
devicetree-discuss@lists.ozlabs.org,
"'Samuel Ortiz'" <sameo@linux.intel.com>,
"'Richard Purdie'" <rpurdie@rpsys.net>,
linux-fbdev@vger.kernel.org,
"'Guennadi Liakhovetski'" <g.liakhovetski+renesas@gmail.com>
Subject: Re: [PATCH v3 3/3] backlight: as3711: add OF support
Date: Mon, 25 Mar 2013 10:14:43 +0000 [thread overview]
Message-ID: <20130325101442.GJ18316@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <00da01ce2917$54856ce0$fd9046a0$%han@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
On Mon, Mar 25, 2013 at 02:12:21PM +0900, Jingoo Han wrote:
> On Saturday, March 23, 2013 1:16 AM, Guennadi Liakhovetski wrote:
> But, there is a typo in comment.
> > + * At least one su2-auto-curr* must be specified iff
> s/iff/if
Are you sure that's a typo? "Iff" is a bit of mathematical jargon
which means "if and only if" that's fairly often used in a computing
context.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-25 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 16:15 [PATCH v3 0/3] DT support for AS3711 MFD, regulator and backlight drivers Guennadi Liakhovetski
2013-03-22 16:15 ` [PATCH v3 1/3] mfd: as3711: add OF support Guennadi Liakhovetski
2013-03-22 16:34 ` Samuel Ortiz
2013-03-22 16:15 ` [PATCH v3 2/3] regulator: " Guennadi Liakhovetski
2013-03-22 18:53 ` Mark Brown
2013-03-22 22:27 ` Guennadi Liakhovetski
2013-03-25 1:08 ` Mark Brown
2013-03-22 16:15 ` [PATCH v3 3/3] backlight: " Guennadi Liakhovetski
2013-03-25 5:12 ` Jingoo Han
2013-03-25 10:14 ` Mark Brown [this message]
2013-03-25 10:52 ` Guennadi Liakhovetski
2013-03-25 23:39 ` Jingoo Han
2013-03-25 22:40 ` Andrew Morton
2013-03-25 23:09 ` Ryan Mallon
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=20130325101442.GJ18316@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=akpm@linux-foundation.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=g.liakhovetski+renesas@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=jg1.han@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=rpurdie@rpsys.net \
--cc=sameo@linux.intel.com \
/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