From: Shawn Guo <shawnguo@kernel.org>
To: Sean Young <sean@mess.org>, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org,
Baoyou Xie <xie.baoyou@sanechips.com.cn>,
Xin Zhou <zhou.xin8@sanechips.com.cn>,
Jun Nie <jun.nie@linaro.org>, Shawn Guo <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Add ZTE zx-irdec remote control driver
Date: Fri, 18 Aug 2017 20:54:20 +0800 [thread overview]
Message-ID: <20170818125418.GM7608@dragon> (raw)
In-Reply-To: <1501420993-21977-1-git-send-email-shawnguo@kernel.org>
On Sun, Jul 30, 2017 at 09:23:10PM +0800, Shawn Guo wrote:
> From: Shawn Guo <shawn.guo@linaro.org>
>
> The series adds dt-bindings and remote control driver for IRDEC block
> found on ZTE ZX family SoCs.
>
> Changes for v2:
> - Add one patch to move generic NEC scancode composing and protocol
> type detection code from ir_nec_decode() into an inline shared
> function, which can be reused by zx-irdec driver.
>
> Shawn Guo (3):
> rc: ir-nec-decoder: move scancode composing code into a shared
> function
> dt-bindings: add bindings document for zx-irdec
> rc: add zx-irdec remote control driver
Hi Sean,
We are getting close to 4.14 merge window. Can we get this into -next
for a bit exposure, if you are fine with the patches?
Shawn
next prev parent reply other threads:[~2017-08-18 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 13:23 [PATCH v2 0/3] Add ZTE zx-irdec remote control driver Shawn Guo
2017-07-30 13:23 ` [PATCH v2 1/3] rc: ir-nec-decoder: move scancode composing code into a shared function Shawn Guo
2017-07-30 13:23 ` [PATCH v2 2/3] dt-bindings: add bindings document for zx-irdec Shawn Guo
2017-08-03 23:36 ` Rob Herring
2017-07-30 13:23 ` [PATCH v2 3/3] rc: add zx-irdec remote control driver Shawn Guo
2017-08-09 13:00 ` Sean Young
2017-08-09 13:48 ` Shawn Guo
2017-08-09 14:42 ` Sean Young
2017-08-18 12:54 ` Shawn Guo [this message]
2017-08-20 20:09 ` [PATCH v2 0/3] Add ZTE " 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=20170818125418.GM7608@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sean@mess.org \
--cc=shawn.guo@linaro.org \
--cc=xie.baoyou@sanechips.com.cn \
--cc=zhou.xin8@sanechips.com.cn \
/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