X86 platform drivers
 help / color / mirror / Atom feed
From: Corentin Chary <corentin.chary@gmail.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: acpi4asus-user@lists.sourceforge.net,
	platform-driver-x86@vger.kernel.org,
	Corentin Chary <corentin.chary@gmail.com>
Subject: [PATCH 1/3] asus-laptop: remove removed features from feature-removal-schedule.txt
Date: Wed, 30 Mar 2011 16:32:31 +0200	[thread overview]
Message-ID: <1301495553-22468-2-git-send-email-corentin.chary@gmail.com> (raw)
In-Reply-To: <1301495553-22468-1-git-send-email-corentin.chary@gmail.com>

commit 3b81cf9d558c57406b4ed9b0d2639113d1d428b6 removed those features.

Signed-off-by: Corentin Chary <corentin.chary@gmail.com>
---
 Documentation/feature-removal-schedule.txt |   20 --------------------
 1 files changed, 0 insertions(+), 20 deletions(-)

diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 274b32d..492e81d 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -387,26 +387,6 @@ Who:	Tejun Heo <tj@kernel.org>
 
 ----------------------------
 
-What:	Support for lcd_switch and display_get in asus-laptop driver
-When:	March 2010
-Why:	These two features use non-standard interfaces. There are the
-	only features that really need multiple path to guess what's
-	the right method name on a specific laptop.
-
-	Removing them will allow to remove a lot of code an significantly
-	clean the drivers.
-
-	This will affect the backlight code which won't be able to know
-	if the backlight is on or off. The platform display file will also be
-	write only (like the one in eeepc-laptop).
-
-	This should'nt affect a lot of user because they usually know
-	when their display is on or off.
-
-Who:	Corentin Chary <corentin.chary@gmail.com>
-
-----------------------------
-
 What:	sysfs-class-rfkill state file
 When:	Feb 2014
 Files:	net/rfkill/core.c
-- 
1.7.3.4

  reply	other threads:[~2011-03-30 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 14:32 [PATCH 0/3] acpi4asus's patchs for 2.6.39-rc1 Corentin Chary
2011-03-30 14:32 ` Corentin Chary [this message]
2011-03-30 14:32 ` [PATCH 2/3] asus-wmi: swap input name and phys Corentin Chary
2011-03-30 14:32 ` [PATCH 3/3] eeepc-wmi: add keys found on EeePC 1215T Corentin Chary
     [not found] ` <1301495553-22468-1-git-send-email-corentin.chary-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-04-01 18:21   ` [PATCH 0/3] acpi4asus's patchs for 2.6.39-rc1 Matthew Garrett

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=1301495553-22468-2-git-send-email-corentin.chary@gmail.com \
    --to=corentin.chary@gmail.com \
    --cc=acpi4asus-user@lists.sourceforge.net \
    --cc=mjg59@srcf.ucam.org \
    --cc=platform-driver-x86@vger.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