All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: Anjelique Melendez <quic_amelende@quicinc.com>,
	dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, collinsd@codeaurora.org,
	bjorn.andersson@linaro.org, skakit@codeaurora.org
Subject: Re: [PATCH v2 1/4] input: misc: pm8941-pwrkey: fix error message
Date: Thu, 27 Jan 2022 14:38:15 -0800	[thread overview]
Message-ID: <CAE-0n505BCr5sJ_21WpAYJmEddsgOtCUMqG=vnjo_VVTjQ3SHQ@mail.gmail.com> (raw)
In-Reply-To: <20220127210024.25597-2-quic_amelende@quicinc.com>

Quoting Anjelique Melendez (2022-01-27 13:00:23)
> Currently, error message reads "failed to set debounce". However,
> code is attempting to read revision not set debounce. Fix this.
>
> Signed-off-by: Anjelique Melendez <quic_amelende@quicinc.com>
> ---

Reviewed-by: Stephen Boyd <swboyd@chromium.org>

  reply	other threads:[~2022-01-27 22:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 21:00 [PATCH v2 0/4] Extend pm8941-pwrkey driver Anjelique Melendez
2022-01-27 21:00 ` [PATCH v2 1/4] input: misc: pm8941-pwrkey: fix error message Anjelique Melendez
2022-01-27 22:38   ` Stephen Boyd [this message]
2022-01-27 21:00 ` [PATCH v2 2/4] input: misc: pm8941-pwrkey: add support for PON GEN3 base addresses Anjelique Melendez
2022-01-27 22:41   ` Stephen Boyd
2022-01-31 18:44     ` Anjelique Melendez
2022-01-27 21:00 ` [PATCH v2 3/4] input: misc: pm8941-pwrkey: add software key press debouncing support Anjelique Melendez
2022-01-27 22:44   ` Stephen Boyd
2022-01-31 18:47     ` Anjelique Melendez
2022-01-27 21:00 ` [PATCH v2 4/4] input: misc: pm8941-pwrkey: simulate missed key press events Anjelique Melendez

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='CAE-0n505BCr5sJ_21WpAYJmEddsgOtCUMqG=vnjo_VVTjQ3SHQ@mail.gmail.com' \
    --to=swboyd@chromium.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=collinsd@codeaurora.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_amelende@quicinc.com \
    --cc=skakit@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.