public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Vinod Koul <vinod.koul@linaro.org>
Cc: linux-input@vger.kernel.org, linux-pm@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Sebastian Reichel <sre@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v3 3/5] dt-bindings: Input: Add additional property to qcom pwrkey
Date: Mon, 25 Jun 2018 11:27:47 -0600	[thread overview]
Message-ID: <20180625172747.GA32100@rob-hp-laptop> (raw)
In-Reply-To: <20180625063840.30173-4-vkoul@kernel.org>

On Mon, Jun 25, 2018 at 12:08:38PM +0530, Vinod Koul wrote:
> Pwrkey and reset have similar properties so add additional
> property for linux,code to use the code for sending events.
> 
> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> Signed-off-by: Vinod Koul <vkoul@kernel.org>
> ---
>  Documentation/devicetree/bindings/input/qcom,pm8941-pwrkey.txt | 9 +++++++++
>  1 file changed, 9 insertions(+)

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2018-06-25 17:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25  6:38 [PATCH v3 0/5] input: pm8941-pwrkey: Add support for reboot reason Vinod Koul
2018-06-25  6:38 ` [PATCH v3 1/5] dt-bindings: power: reset: Add qcom pon binding Vinod Koul
2018-06-25 17:27   ` Rob Herring
2018-06-26  3:51     ` Vinod
2018-06-26 14:47       ` Rob Herring
2018-06-26 15:25         ` Vinod
2018-06-25  6:38 ` [PATCH v3 2/5] power: reset: qcom-pon: Add Qcom PON driver Vinod Koul
2018-06-25  6:38 ` [PATCH v3 3/5] dt-bindings: Input: Add additional property to qcom pwrkey Vinod Koul
2018-06-25 17:27   ` Rob Herring [this message]
2018-06-25  6:38 ` [PATCH v3 4/5] input: pm8941-pwrkey: Abstract register offsets and event code Vinod Koul
2018-06-25  6:38 ` [PATCH v3 5/5] input: pm8941-pwrkey: Add resin entry Vinod Koul

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=20180625172747.GA32100@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=vinod.koul@linaro.org \
    --cc=vkoul@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