lists.openwall.net   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  linux-cve-announce  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]
Message-ID: <CAJZ5v0jvgpXr8iFO44Hzii_19B1r=+peeuMGpokaW=jep2SVvg@mail.gmail.com>
Date:   Thu, 26 Jan 2017 11:56:07 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Mark Rutland <mark.rutland@....com>,
        Mark Brown <broonie@...nel.org>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Lu Baolu <baolu.lu@...ux.intel.com>,
        "Rafael J . Wysocki" <rafael@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Revert "regulator: fixed: add support for ACPI interface"

On Wed, Jan 25, 2017 at 8:30 PM, Mark Rutland <mark.rutland@....com> wrote:
> This reverts commit 13bed58ce8748d430a26e353a09b89f9d613a71f.
>
> While there does appear to be a practical need to manage regulators on ACPI
> systems, using ad-hoc properties to describe regulators to the kernel presents
> a number of problems (especially should ACPI gain first class support for such
> things), and there are ongoing discussions as to how to manage this.
>
> Until there is a rough consensus, revert commit 13bed58ce8748d43,

FWIW, I overlooked this one somehow and I agree that it shouldn't have
been applied in the first place.

Did it actually go to linux-acpi, BTW?

Thanks,
Rafael

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ