From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 0/6] OLPC 1.75 Keyboard/Touchpad fixes
Date: Thu, 15 Nov 2018 11:15:30 -0800 [thread overview]
Message-ID: <20181115191530.GB212221@dtor-ws> (raw)
In-Reply-To: <20181112023029.648408-1-lkundrak@v3.sk>
On Mon, Nov 12, 2018 at 03:30:23AM +0100, Lubomir Rintel wrote:
> This makes keyboard/touchpad work on a DT MMP2 platform.
>
> Changes since v1:
> - Collected Acks
> - Replaced "Input: olpc_apsp: depend on CONFIG_OF" patch with "Input:
> olpc_apsp: drop CONFIG_OLPC dependency", since it was correctly
> pointed out that the driver doesn't actually depend on OF.
> - Dropped "Input: olpc_apsp: allocate the GPIOs used" and "dt-bindings:
> olpc,ap-sp: add GPIO lines" since at the moment they are not useful
> for much more than documenting the lines the SP uses and actually
> claiming them was deemed not to be a good idea.
> - Fixed error handling in the "enable the SP clock" patch.
Applied the series, thank you.
--
Dmitry
prev parent reply other threads:[~2018-11-15 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 2:30 [PATCH v2 0/6] OLPC 1.75 Keyboard/Touchpad fixes Lubomir Rintel
2018-11-12 2:30 ` [PATCH v2 1/6] dt-bindings: olpc,ap-sp: add clock Lubomir Rintel
2018-11-12 2:30 ` [PATCH v2 2/6] dt-bindings: marvell,mmp2: Add clock id for the SP clock Lubomir Rintel
2018-11-12 2:30 ` [PATCH v2 3/6] clk: mmp2: add " Lubomir Rintel
2018-11-12 2:30 ` [PATCH v2 4/6] Input: olpc_apsp: drop CONFIG_OLPC dependency Lubomir Rintel
2018-11-12 2:30 ` [PATCH v2 5/6] Input: olpc_apsp: check FIFO status on open(), not probe() Lubomir Rintel
2018-11-12 2:30 ` [PATCH v2 6/6] Input: olpc_apsp: enable the SP clock Lubomir Rintel
2018-11-15 19:15 ` Dmitry Torokhov [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=20181115191530.GB212221@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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