From: Sean Young <sean@mess.org>
To: Sean Wang <sean.wang@mediatek.com>
Cc: mchehab@kernel.org, mchehab@osg.samsung.com,
Andi Shyti <andi.shyti@samsung.com>,
hdegoede@redhat.com, hkallweit1@gmail.com, robh+dt@kernel.org,
mark.rutland@arm.com, matthias.bgg@gmail.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 0/4] media: rc: add support for IR receiver on MT7622 SoC
Date: Wed, 2 Aug 2017 11:02:58 +0100 [thread overview]
Message-ID: <20170802100257.cn5nfotpccdwsruo@gofer.mess.org> (raw)
In-Reply-To: <1501640647.17690.25.camel@mtkswgap22>
Hi Sean,
On Wed, Aug 02, 2017 at 10:24:07AM +0800, Sean Wang wrote:
> Hi, Mauro and Sean
>
> Just a gentle ping on the whole patchset porting MediaTek CIR to another
> platform.
I'm creating the rc-core pull request, should be done by the end of the week.
Sean
prev parent reply other threads:[~2017-08-02 10:03 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
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 [this message]
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=20170802100257.cn5nfotpccdwsruo@gofer.mess.org \
--to=sean@mess.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@kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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).