Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754642Ab3FOUfs (ORCPT ); Sat, 15 Jun 2013 16:35:48 -0400 Received: from mail-ee0-f53.google.com ([74.125.83.53]:46773 "EHLO mail-ee0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754532Ab3FOUfq (ORCPT ); Sat, 15 Jun 2013 16:35:46 -0400 Date: Sat, 15 Jun 2013 22:35:34 +0200 From: Daniel Vetter To: "Rafael J. Wysocki" Cc: Daniel Vetter , Matthew Garrett , Aaron Lu , "linux-acpi@vger.kernel.org" , Seth Forshee , "Lee, Chun-Yi" , "daniel.vetter@ffwll.ch" , "intel-gfx@lists.freedesktop.org" , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , Len Brown , Zhang Rui , Aaron Lu , Alex Deucher Subject: Re: [PATCH 3/3] i915: Don't provide ACPI backlight interface if firmware expects Windows 8 Message-ID: <20130615203534.GC6424@phenom.ffwll.local> Mail-Followup-To: "Rafael J. Wysocki" , Matthew Garrett , Aaron Lu , "linux-acpi@vger.kernel.org" , Seth Forshee , "Lee, Chun-Yi" , "intel-gfx@lists.freedesktop.org" , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , Len Brown , Zhang Rui , Aaron Lu , Alex Deucher References: <1370818899-8595-1-git-send-email-matthew.garrett@nebula.com> <20130615151628.GA9868@srcf.ucam.org> <20130615182942.GA6424@phenom.ffwll.local> <6834259.1uPUZ8EFRd@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6834259.1uPUZ8EFRd@vostro.rjw.lan> X-Operating-System: Linux phenom 3.10.0-rc5+ User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1472 Lines: 36 On Sat, Jun 15, 2013 at 10:27:06PM +0200, Rafael J. Wysocki wrote: > On Saturday, June 15, 2013 08:29:42 PM Daniel Vetter wrote: > > Hi all, > > > > So to me it looks like the discussion is going in circles a bit, hence let > > me drop my maintainer-opinion here: > > > > 1. Matthew's patch series here looks reasonable, and if it fixes a bunch > > of systems (which it seems to) it has my Ack and imo should go in. If acpi > > maintainers can smash their Ack onto the acpi parts I'd very much like to > > merge this into drm-intel-next, that should give us the most coverage for > > intel systems. > > > > Len, Rafael, are you ok with the acpi part of this and merging it through > > drm-intel-next? > > It has to go through the ACPI tree because of the ACPICA patch that needs to > be synchronized with the ACPICA upstream. Sorry. No problem, since we're pretty close to the merge window that would have at most resulted in a few more weeks of testing in i915 trees anyway. -rc kernels should still give us plenty of time to catch fallout, if there is any. > That said, I'm going to take this patchset. Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- 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/