From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Fabien Parent <fparent@baylibre.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/8] dt-bindings: input: mtk-pmic-keys: add MT6359 binding definition
Date: Thu, 28 Apr 2022 09:53:27 +0200 [thread overview]
Message-ID: <1e3afa05-2e2f-fb0a-19a3-5a7a6af50863@linaro.org> (raw)
In-Reply-To: <20220426135313.245466-2-fparent@baylibre.com>
On 26/04/2022 15:53, Fabien Parent wrote:
> Add binding definition for the support of the MT6359 keyboard driver.
>
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> ---
> v2: no changes
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-28 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220426135313.245466-1-fparent@baylibre.com>
2022-04-26 13:53 ` Fabien Parent
2022-04-28 7:53 ` Krzysztof Kozlowski [this message]
2022-04-26 13:53 ` [PATCH v2 2/8] mfd: add missing defines necessary for mtk-pmic-keys support Fabien Parent
2022-04-27 6:10 ` Macpaul Lin
2022-04-26 13:53 ` [PATCH v2 3/8] mfd: mt6397-core: add resources for PMIC keys for MT6359 Fabien Parent
2022-04-26 13:53 ` [PATCH v2 4/8] Input: mtk-pmic-keys: rename platform data struct Fabien Parent
2022-04-26 13:53 ` [PATCH v2 5/8] Input: mtk-pmic-keys: add field to store if PMIC has key release IRQs Fabien Parent
2022-04-26 13:53 ` [PATCH v2 6/8] Input: keyboard: mtk-pmic-keys: add support for MT6359 Fabien Parent
2022-04-26 13:53 ` [PATCH v2 7/8] arm64: dts: mediatek: mt6359: add node for PMIC keys support Fabien Parent
2022-04-26 13:53 ` [PATCH v2 8/8] arm64: dts: mediatek: mt8195-demo: define PMIC keys available Fabien Parent
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=1e3afa05-2e2f-fb0a-19a3-5a7a6af50863@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=fparent@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®