lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 6 Dec 2020 09:07:05 +0200
From:   Leon Romanovsky <>
To:     Maximilian Luz <>,
        Greg Kroah-Hartman <>
Cc:, Hans de Goede <>,
        Mark Gross <>,
        Andy Shevchenko <>,
        Barnabás Pőcze <>,
        Arnd Bergmann <>, Rob Herring <>,
        Jiri Slaby <>,
        "Rafael J . Wysocki" <>,
        Len Brown <>,
        Steven Rostedt <>,
        Ingo Molnar <>,
        Masahiro Yamada <>,
        Michal Marek <>,
        Jonathan Corbet <>,
        Blaž Hrastnik <>,
        Dorian Stoll <>,,,,,
Subject: Re: [PATCH v2 0/9] Add support for Microsoft Surface System
 Aggregator Module

On Thu, Dec 03, 2020 at 10:26:31PM +0100, Maximilian Luz wrote:
> Hello,
> Here is version two of the Surface System Aggregator Module (SAM/SSAM)
> driver series, adding initial support for the embedded controller on 5th
> and later generation Microsoft Surface devices. Initial support includes
> the ACPI interface to the controller, via which battery and thermal
> information is provided on some of these devices.
> The previous version and cover letter detailing what this series is
> about can be found at
> This patch-set can also be found at the following repository and
> reference, if you prefer to look at a kernel tree instead of these
> emails:
> tags/s/surface-aggregator/v2
> Thank you all for the feedback to v1, I hope I have addressed all
> comments.

I think that it is too far fetched to attempt and expose UAPI headers
for some obscure char device that we are all know won't be around in
a couple of years from now due to the nature of how this embedded world

More on that, the whole purpose of proposed interface is to debug and
not intended to be used by any user space code.

Also the idea that you are creating new bus just for this device doesn't
really sound right. I recommend you to take a look on auxiliary bus and
use it or come with very strong justifications why it is not fit yet.

I'm sorry to say, but this series is not ready to be merged yet.

NAK: Leon Romanovsky <>


Powered by blists - more mailing lists