From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: mchehab@kernel.org
Cc: linux-media <linux-media@vger.kernel.org>,
carlo@caione.org, khilman@baylibre.com,
linux-amlogic@lists.infradead.org, robh+dt@kernel.org,
mark.rutland@arm.com, narmstrong@baylibre.com,
linux-arm-kernel@lists.infradead.org, afaerber@suse.de,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: devicetree: meson-ir: "linux,rc-map-name" is supported
Date: Wed, 1 Feb 2017 23:26:14 +0100 [thread overview]
Message-ID: <CAFBinCDF2d36E2hp7w_ehqdErdZPK9maQLpBmqMoGMPZmTTqqQ@mail.gmail.com> (raw)
In-Reply-To: <20170201221415.22794-1-martin.blumenstingl@googlemail.com>
On Wed, Feb 1, 2017 at 11:14 PM, Martin Blumenstingl
<martin.blumenstingl@googlemail.com> wrote:
> The driver already parses the "linux,rc-map-name" property. Add this
> information to the documentation so .dts maintainers don't have to look
> it up in the source-code.
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
> Acked-by: Rob Herring <robh@kernel.org>
> ---
> Changes since v1:
> - removed character which shows up as whitespace from subject
I have verified that I really sent this without a whitespace (I'm
using git send-email, so the patch is not mangled by some webmailer) -
unfortunately it seems to appear again (maybe one of the receiving
mail-servers or the mailing-list software does something weird here).
@Mauro: can you handle this when you merge the patch - or do you want
me to push this to some git repo from which you can pull?
> - added Rob Herring's ACK
>
> Documentation/devicetree/bindings/media/meson-ir.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/media/meson-ir.txt b/Documentation/devicetree/bindings/media/meson-ir.txt
> index e7e3f3c4fc8f..efd9d29a8f10 100644
> --- a/Documentation/devicetree/bindings/media/meson-ir.txt
> +++ b/Documentation/devicetree/bindings/media/meson-ir.txt
> @@ -8,6 +8,9 @@ Required properties:
> - reg : physical base address and length of the device registers
> - interrupts : a single specifier for the interrupt from the device
>
> +Optional properties:
> + - linux,rc-map-name: see rc.txt file in the same directory.
> +
> Example:
>
> ir-receiver@c8100480 {
> --
> 2.11.0
>
next prev parent reply other threads:[~2017-02-01 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 21:21 [PATCH] Documentation: devicetree: meson-ir: "linux,rc-map-name" is supported Martin Blumenstingl
2017-02-01 17:47 ` Rob Herring
2017-02-01 18:22 ` [PATCH] Documentation: devicetree: meson-ir: "linux, rc-map-name" " Andreas Färber
2017-02-01 22:14 ` [PATCH v2] Documentation: devicetree: meson-ir: "linux,rc-map-name" " Martin Blumenstingl
2017-02-01 22:26 ` Martin Blumenstingl [this message]
2017-02-01 22:49 ` Sean Young
2017-02-02 13:04 ` Andreas Färber
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=CAFBinCDF2d36E2hp7w_ehqdErdZPK9maQLpBmqMoGMPZmTTqqQ@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=afaerber@suse.de \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).