From: Pavel Machek <pavel@ucw.cz>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, javier@dowhile0.org,
jacek.anaszewski@gmail.com, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: [PATCH v2 1/3] dt: bindings: Document DT bindings for Analog devices as3645a
Date: Mon, 28 Aug 2017 13:09:52 +0200 [thread overview]
Message-ID: <20170828110951.GC492@amd> (raw)
In-Reply-To: <46aaf723-a657-3b43-7be7-8d899d3db9c3@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Hi!
> Thanks for the review!
>
> On 08/28/17 13:33, Pavel Machek wrote:
> > Hi!
> >
> >> +
> >> +Ranges below noted as [a, b] are closed ranges between a and b, i.e. a
> >> +and b are included in the range.
> >
> > Normally I've seen <a, b> for closed ranges, (a, b) for open
> > ranges. Is that different in your country?
>
> I guess there are different notations. :-) I've seen regular parentheses
> being used for open ranges, too, but not < and >.
>
> Open range is documented in a related well written Wikipedia article:
>
> <URL:https://en.wikipedia.org/wiki/Open_range>
>
> Are there such open ranges in Czechia? For instance, reindeer generally
> roam freely in Finnish Lappland.
:-). Well, we have pigs and roes roaming freely in the woods, but
would not normally call it open range.
> What comes to the patch, I guess "interval" could be a more appropriate
> term to use in this case:
>
> <URL:https://en.wikipedia.org/wiki/Interval_(mathematics)>
>
> The patch is in line with the Wikipedia article in notation but not in
> terminology. I'll send a fix.
Ok, that was really nitpicking, thanks!
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-08-28 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 21:24 [PATCH v2 0/3] AS3645A flash support Sakari Ailus
2017-08-19 21:24 ` [PATCH v2 1/3] dt: bindings: Document DT bindings for Analog devices as3645a Sakari Ailus
2017-08-22 18:34 ` Jacek Anaszewski
[not found] ` <20170819212410.3084-2-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-08-23 0:28 ` Rob Herring
2017-08-23 7:33 ` Sakari Ailus
2017-08-28 10:33 ` Pavel Machek
2017-08-28 10:48 ` Sakari Ailus
2017-08-28 11:09 ` Pavel Machek [this message]
[not found] ` <20170819212410.3084-1-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-08-19 21:24 ` [PATCH v2 2/3] leds: as3645a: Add LED flash class driver Sakari Ailus
2017-08-19 21:42 ` [PATCH v2.1 " Sakari Ailus
2017-08-20 10:09 ` Jacek Anaszewski
2017-08-20 10:12 ` Jacek Anaszewski
[not found] ` <fc6c7893-863b-53ff-48e3-d14297364e5d-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-21 13:53 ` Sakari Ailus
2017-08-21 19:03 ` Jacek Anaszewski
2017-08-21 20:59 ` Sakari Ailus
2017-08-19 21:24 ` [PATCH v2 3/3] arm: dts: omap3: N9/N950: Add AS3645A camera flash Sakari Ailus
2017-08-21 19:57 ` [PATCH v2.1 " Sakari Ailus
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=20170828110951.GC492@amd \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=jacek.anaszewski@gmail.com \
--cc=javier@dowhile0.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@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;
as well as URLs for NNTP newsgroup(s).