linux-kernel - Re: [Intel-gfx] [PATCH] i915: Add a Kconfig option to turn on i915.preliminary_hw

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130815113622.GB776@phenom.ffwll.local>
Date:	Thu, 15 Aug 2013 13:36:23 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	Damien Lespiau <damien.lespiau@...el.com>
Cc:	Josh Triplett <josh@...htriplett.org>,
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
	intel-gfx@...ts.freedesktop.org, David Airlie <airlied@...ux.ie>,
	Daniel Vetter <daniel.vetter@...ll.ch>
Subject: Re: [Intel-gfx] [PATCH] i915: Add a Kconfig option to turn on
 i915.preliminary_hw_support by default

On Thu, Aug 15, 2013 at 11:55:33AM +0100, Damien Lespiau wrote:
> On Tue, Aug 13, 2013 at 04:23:17PM -0700, Josh Triplett wrote:
> > When building kernels for a preliminary hardware target, having to add a
> > kernel command-line option can prove inconvenient.  Add a Kconfig option
> > that changes the default of this option to 1.
> 
> FWIW, I like it (and had something similar in mind for this on other
> little parameters/debug features). 
> 
> Reviewed-by: Damien Lespiau <damien.lespiau@...el.com>
> 
> It doesn't apply cleanly to drm-intel/drm-intel-nightly which is the
> preferred branch to base patches on. Daniel might fix this himself as
> this is rather trivial to solve.

Yeah, -nightly is the preferred branch for everything. Queued for -next,
thanks for the patch.
-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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/