From: Maximilian Luz <luzmaximilian@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Mark Gross <markgross@kernel.org>,
Andy Shevchenko <andy@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-input@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 2/2] platform/surface: Remove Surface 3 Button driver
Date: Thu, 24 Feb 2022 14:09:10 +0100 [thread overview]
Message-ID: <fc05d480-49f4-bb6f-3f21-531085ec226f@gmail.com> (raw)
In-Reply-To: <20220224110241.9613-3-hdegoede@redhat.com>
On 2/24/22 12:02, Hans de Goede wrote:
> The Surface 3 buttons are now handled by the generic soc_button_array
> driver. As part of adding support to soc_button_array the ACPI code
> now instantiates a platform_device rather then an i2c_client so there
> no longer is an i2c_client for this driver to bind to.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Looks good to me.
Reviewed-by: Maximilian Luz <luzmaximilian@gmail.com
next prev parent reply other threads:[~2022-02-24 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 11:02 [PATCH 0/2] Input: Replace surface3_button code with soc_button_array Hans de Goede
2022-02-24 11:02 ` [PATCH 1/2] Input: soc_button_array - add support for Microsoft Surface 3 (MSHW0028) buttons Hans de Goede
2022-02-24 13:08 ` Maximilian Luz
2022-02-25 19:57 ` Rafael J. Wysocki
2022-03-01 20:41 ` Dmitry Torokhov
2022-02-24 11:02 ` [PATCH 2/2] platform/surface: Remove Surface 3 Button driver Hans de Goede
2022-02-24 13:09 ` Maximilian Luz [this message]
2022-02-25 16:48 ` [PATCH 0/2] Input: Replace surface3_button code with soc_button_array Andy Shevchenko
2022-03-02 11:34 ` Hans de Goede
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=fc05d480-49f4-bb6f-3f21-531085ec226f@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=andy@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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;
as well as URLs for NNTP newsgroup(s).