From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Mohammad Rasim <mohammad.rasim96@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v3 1/2] dt-bindings: Add vendor prefix for Videostrong
Date: Sat, 30 Nov 2019 14:45:22 +0100 [thread overview]
Message-ID: <CAFBinCCg5GdHprEKfXU1LBtgQi2G7P30=bmLh8Acrn82vYGfeg@mail.gmail.com> (raw)
In-Reply-To: <20191130115824.31778-2-mohammad.rasim96@gmail.com>
Hi Mohammad,
On Sat, Nov 30, 2019 at 12:58 PM Mohammad Rasim
<mohammad.rasim96@gmail.com> wrote:
>
> Videostrong Technology Co., Ltd., A manufacturer of Android Players & STB
> (Android with DVB Hybrid box & DVB-T2/S2/C/ISDB-T/DTMB-TH/ATSC )as well as
the space after ATSC should be after the ")"
> HD media players.
>
> Signed-off-by: Mohammad Rasim <mohammad.rasim96@gmail.com>
with above typo fixed:
Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-11-30 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 11:58 [PATCH v3 0/2] add support for videostrong KII Pro Mohammad Rasim
2019-11-30 11:58 ` [PATCH v3 1/2] dt-bindings: Add vendor prefix for Videostrong Mohammad Rasim
2019-11-30 13:45 ` Martin Blumenstingl [this message]
2019-11-30 17:11 ` Mohammad Rasim
2019-11-30 11:58 ` [PATCH v3 2/2] arm64: dts: meson-gxbb: add support for Mohammad Rasim
2019-11-30 13:59 ` Martin Blumenstingl
2019-11-30 17:47 ` Mohammad Rasim
2019-11-30 18:57 ` Martin Blumenstingl
2019-11-30 19:07 ` Mohammad Rasim
2019-11-30 19:12 ` Mohammad Rasim
2019-11-30 19:25 ` Martin Blumenstingl
2019-11-30 14:00 ` [PATCH v3 0/2] add support for videostrong KII Pro Martin Blumenstingl
2019-11-30 17:51 ` Mohammad Rasim
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='CAFBinCCg5GdHprEKfXU1LBtgQi2G7P30=bmLh8Acrn82vYGfeg@mail.gmail.com' \
--to=martin.blumenstingl@googlemail.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mohammad.rasim96@gmail.com \
--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).