From: Rob Herring <robh@kernel.org>
To: sean.wang@mediatek.com
Cc: mchehab@osg.samsung.com, sean@mess.org, hdegoede@redhat.com,
hkallweit1@gmail.com, mark.rutland@arm.com,
matthias.bgg@gmail.com, andi.shyti@samsung.com,
hverkuil@xs4all.nl, ivo.g.dimitrov.75@gmail.com,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/4] dt-bindings: media: mtk-cir: Add support for MT7622 SoC
Date: Thu, 6 Jul 2017 13:56:27 -0500 [thread overview]
Message-ID: <20170706185627.zqhgwtc7m7buf3kg@rob-hp-laptop> (raw)
In-Reply-To: <a778a3a33a273f00d3ff071d62fe672a207d949c.1498794408.git.sean.wang@mediatek.com>
On Fri, Jun 30, 2017 at 02:03:04PM +0800, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> Document the devicetree bindings for CIR on MediaTek MT7622
> SoC.
>
> Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> ---
> Documentation/devicetree/bindings/media/mtk-cir.txt | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-07-06 18:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170630060312epcas4p351a77795e8469640d5177039f6b1955d@epcas4p3.samsung.com>
2017-06-30 6:03 ` [PATCH v1 0/4] media: rc: add support for IR receiver on MT7622 SoC sean.wang
2017-06-30 6:03 ` [PATCH v1 1/4] dt-bindings: media: mtk-cir: Add support for " sean.wang
2017-07-06 18:56 ` Rob Herring [this message]
2017-06-30 6:03 ` [PATCH v1 2/4] media: rc: mtk-cir: add platform data to adapt into various hardware sean.wang
2017-06-30 6:03 ` [PATCH v1 3/4] media: rc: mtk-cir: add support for MediaTek MT7622 SoC sean.wang
2017-06-30 6:03 ` [PATCH v1 4/4] MAINTAINERS: add entry for MediaTek CIR driver sean.wang
2017-07-04 10:10 ` [PATCH v1 0/4] media: rc: add support for IR receiver on MT7622 SoC Andi Shyti
2017-08-02 2:24 ` Sean Wang
2017-08-02 10:02 ` Sean Young
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=20170706185627.zqhgwtc7m7buf3kg@rob-hp-laptop \
--to=robh@kernel.org \
--cc=andi.shyti@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=hkallweit1@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@osg.samsung.com \
--cc=sean.wang@mediatek.com \
--cc=sean@mess.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).