Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754342Ab3JFUkp (ORCPT ); Sun, 6 Oct 2013 16:40:45 -0400 Received: from mail-la0-f51.google.com ([209.85.215.51]:58194 "EHLO mail-la0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752380Ab3JFUko (ORCPT ); Sun, 6 Oct 2013 16:40:44 -0400 MIME-Version: 1.0 In-Reply-To: <20131006203353.GA19795@srcf.ucam.org> References: <1380820383-23336-1-git-send-email-felipe.contreras@gmail.com> <20131004161226.GA22784@srcf.ucam.org> <20131006203353.GA19795@srcf.ucam.org> Date: Sun, 6 Oct 2013 15:40:42 -0500 Message-ID: Subject: Re: [PATCH] acpi: update win8 OSI blacklist From: Felipe Contreras To: Matthew Garrett Cc: Linux Kernel Mailing List , ACPI Devel Maling List , "Rafael J. Wysocki" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1179 Lines: 27 On Sun, Oct 6, 2013 at 3:33 PM, Matthew Garrett wrote: > On Sun, Oct 06, 2013 at 03:29:10PM -0500, Felipe Contreras wrote: >> On Fri, Oct 4, 2013 at 11:12 AM, Matthew Garrett wrote: >> > On Thu, Oct 03, 2013 at 12:13:03PM -0500, Felipe Contreras wrote: >> >> More people have reported they need this for their machines to work >> >> correctly. >> > >> > Can you add a comment to each indicating why they're being added so we >> > can easily remove them again once the problem is fixed? >> >> Because that's what users report: >> https://bugzilla.kernel.org/show_bug.cgi?id=60682 > > Yes. For each entry, add a comment describing the specific bug seen. In case you didn't hear, the plan was to add an entry if a user reports the backlight not working correctly, and acpi_osi="!Windows 2012" fixing it with no negative effects. and that's what users did in bug #60682. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/