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: <200701051202.31208.lenb@kernel.org>
Date:	Fri, 5 Jan 2007 12:02:30 -0500
From:	Len Brown <lenb@...nel.org>
To:	Mattia Dongili <malattia@...ux.it>
Cc:	Richard Hughes <hughsient@...il.com>,
	Andrew Morton <akpm@...l.org>,
	Stelian Pop <stelian@...ies.net>,
	Ismail Donmez <ismail@...dus.org.tr>,
	Andrea Gelmini <gelma@...ma.net>, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, Cacy Rodney <cacy-rodney-cacy@...n.pl>
Subject: Re: sonypc with Sony Vaio VGN-SZ1VP

> > Well, HAL has used it for changing the brightness for the last year or
> > so: /proc/acpi/sony/brightness
> > 
> > Although if you use a new enough HAL (CVS), the laptop will be supported
> > via the shiny new backlight class.
> 
> great, -mm already has the /sys/class/backlight in place for sony_acpi
> and I suppose the /proc entry can be kept until 2.6.20 is released, i.e.
> just before pushing things for .21.
> 
> Len, would you allow it?

Sure, no problem.
Checking it into my tree with /proc/acpi/sony is
no different than what is in -mm today.

When we push upstream, however, the /proc/acpi/sony part should be gone,
or at least scheduled for removal.

I suggest a sub CONFIG option under CONFIG_SONY_ACPI, say,
CONFIG_SONY_ACPI_PROCFS so you can #ifdef the code that
is going away.

thanks for stepping forward Mattia,
-Len
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ