linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Merlijn Wajer" <merlijn@wizzup.org>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	"Darren Hart (VMware)" <dvhart@infradead.org>,
	"Mattias Jacobsson" <2pi@mok.nu>,
	"Sebastian Reichel" <sebastian.reichel@collabora.com>,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 0/2] Add SW_MACHINE_COVER key
Date: Tue, 25 Feb 2020 06:31:48 -0800	[thread overview]
Message-ID: <20200225143148.GG37466@atomide.com> (raw)
In-Reply-To: <20200215170216.14397-1-merlijn@wizzup.org>

* Merlijn Wajer <merlijn@wizzup.org> [200215 09:01]:
> this series adds the sw_machine_cover key, and changes the nokia n900 dts to
> expose the key via gpio-keys.

Looks good to me. It's probably best to apply these via the input subsystem
tree because of the generci SW_MACHINE_COVER key addition. For both patches:

Acked-by: Tony Lindgren <tony@atomide.com>

  parent reply	other threads:[~2020-02-25 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-15 17:02 [PATCH 0/2] Add SW_MACHINE_COVER key Merlijn Wajer
2020-02-15 17:02 ` [PATCH 1/2] Input: add `SW_MACHINE_COVER` Merlijn Wajer
2020-02-15 17:02 ` [PATCH 2/2] ARM: dts: n900: remove mmc1 card detect gpio Merlijn Wajer
2020-02-25 14:31 ` Tony Lindgren [this message]
2020-04-15 13:29 ` [PATCH 0/2] Add SW_MACHINE_COVER key Merlijn Wajer
2020-06-08 23:56   ` Merlijn Wajer
2020-06-09 11:21     ` Pavel Machek
2020-06-12 12:53 Merlijn Wajer
2020-06-16 10:50 ` Pavel Machek
2020-06-30 19:29 ` Dmitry Torokhov

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=20200225143148.GG37466@atomide.com \
    --to=tony@atomide.com \
    --cc=2pi@mok.nu \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=merlijn@wizzup.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    /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;
as well as URLs for NNTP newsgroup(s).