On 1/23/2017 11:46 PM, Dmitry Torokhov wrote:
On Mon, Jan 23, 2017 at 05:00:38PM +0200, Andy Shevchenko wrote:
On Sun, 2017-01-22 at 23:38 -0800, Dmitry Torokhov wrote:
When augmenting ACPI-enumerated devices with additional property data
based
on DMI info, a module has often several potential
On Mon, Jan 23, 2017 at 05:00:38PM +0200, Andy Shevchenko wrote:
> On Sun, 2017-01-22 at 23:38 -0800, Dmitry Torokhov wrote:
> > When augmenting ACPI-enumerated devices with additional property data
> > based
> > on DMI info, a module has often several potential property sets, with
> > only
> > one
On Sun, 2017-01-22 at 23:38 -0800, Dmitry Torokhov wrote:
> When augmenting ACPI-enumerated devices with additional property data
> based
> on DMI info, a module has often several potential property sets, with
> only
> one being active on a given box. In order to save memory it should be
> possible
On Sun, Jan 22, 2017 at 11:38:48PM -0800, Dmitry Torokhov wrote:
> When augmenting ACPI-enumerated devices with additional property data based
> on DMI info, a module has often several potential property sets, with only
> one being active on a given box. In order to save memory it should be
> possi
When augmenting ACPI-enumerated devices with additional property data based
on DMI info, a module has often several potential property sets, with only
one being active on a given box. In order to save memory it should be
possible to mark everything and __initdata or __initconst, execute DMI
match e
5 matches
Mail list logo