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] [day] [month] [year] [list]
Message-ID: <20120318190034.GI4286@phenom.ffwll.local>
Date:	Sun, 18 Mar 2012 20:00:34 +0100
From:	Daniel Vetter <daniel@...ll.ch>
To:	Carsten Emde <C.Emde@...dl.org>
Cc:	David Airlie <airlied@...ux.ie>,
	Valdis Kletnieks <Valdis.Kletnieks@...edu>,
	LKML <linux-kernel@...r.kernel.org>,
	DRI <dri-devel@...ts.freedesktop.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Paul Menzel <paulepanter@...rs.sourceforge.net>
Subject: Re: [V5 PATCH 0/4] Provide workarounds to use DRM/KMS with broken
 graphics hardware

On Thu, Mar 15, 2012 at 03:56:23PM +0100, Carsten Emde wrote:
> Changes from V4 to V5:
> 
> 1. Split the previous patch 2/2 into three patches to separately i) add the
> module parameter, ii) add the quirk infrastructure, and iii) actually quirk
> the related machine.
> 
> 2. Rename the module parameter variable to i915_panel_invert_brightness.
> 
> 3. Make the module parameter variable tristate to either ignore the
> quirk, consider the quirk, if any, or force inversion.
> 
> 4. Print an instruction along the description of the module parameter to
> encourage people sending machine data, should another machine be found
> that needs to be quirked.
> 
> 5. Introduce the function intel_panel_compute_brightness where the
> brightness calculation is handled.
> 
> Thanks, Chris, for these very valuable suggestions.

I've picked up patches 2-4 from this series, thanks.
-Daniel
-- 
Daniel Vetter
Mail: daniel@...ll.ch
Mobile: +41 (0)79 365 57 48
--
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