From: Maximilian Luz <luzmaximilian@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>, Sebastian Reichel <sre@kernel.org>
Cc: linux-pm@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] power: supply: Add battery and AC drivers for Surface devices
Date: Wed, 17 Mar 2021 18:47:31 +0100 [thread overview]
Message-ID: <f124e477-2786-d842-5694-13aa4146ba34@gmail.com> (raw)
In-Reply-To: <edcbe108-8cd7-4034-222f-c8ce56918dee@redhat.com>
On 3/17/21 6:39 PM, Hans de Goede wrote:
> Hi,
>
> On 3/9/21 1:05 AM, Maximilian Luz wrote:
>> This series provides battery and AC drivers for Microsoft Surface
>> devices, where this information is provided via an embedded controller
>> (the Surface System Aggregator Module, SSAM) instead of the usual ACPI
>> interface.
>>
>> Specifically, 7th generation Surface devices, i.e. Surface Pro 7,
>> Surface Book 3, Surface Laptop 3, as well as the Surface Laptop Go use
>> this new interface.
>>
>> Note: This series depends on the
>>
>> platform/surface: Add Surface Aggregator device registry
>>
>> series. More specifically patch
>>
>> platform/surface: Set up Surface Aggregator device registry
>>
>> The full series has been merged into the for-next branch of the
>> platform-drivers-x86 tree [1]. The commit in question can be found at
>> [2].
>>
>> [1]: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=for-next
>> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next&id=fc622b3d36e6d91330fb21506b9ad1e3206a4dde
>
> Sebastian, I guess you want a pull-req from an immutable branch from me for
> that dependend commit and then you will merge these 2 patches ?
>
> Maximillian, this only needs that commit right, or would it be better if
> I send Sebastian a pull-req for a branch with the entire series?
The entire series would be better, I think.
Strictly speaking, it only requires the mentioned commit to compile
successfully, but if anyone would want to test this they'd need the full
series (or at least the battery/power subsystem commit) due to the
device instantiation.
Same reasoning applies to the HID series.
Thanks,
Max
next prev parent reply other threads:[~2021-03-17 17:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 0:05 [PATCH 0/2] power: supply: Add battery and AC drivers for Surface devices Maximilian Luz
2021-03-09 0:05 ` [PATCH 1/2] power: supply: Add battery driver for Surface Aggregator Module Maximilian Luz
2021-04-05 15:37 ` Sebastian Reichel
2021-04-05 19:07 ` Maximilian Luz
2021-04-05 21:32 ` Sebastian Reichel
2021-04-05 22:34 ` Maximilian Luz
2021-03-09 0:05 ` [PATCH 2/2] power: supply: Add AC " Maximilian Luz
2021-04-05 15:47 ` Sebastian Reichel
2021-04-05 19:08 ` Maximilian Luz
2021-03-17 17:39 ` [PATCH 0/2] power: supply: Add battery and AC drivers for Surface devices Hans de Goede
2021-03-17 17:47 ` Maximilian Luz [this message]
2021-03-17 17:49 ` Hans de Goede
2021-03-27 20:49 ` Maximilian Luz
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=f124e477-2786-d842-5694-13aa4146ba34@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sre@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 read-only IMAP folder(s) and NNTP newsgroup(s).