On Thu, Aug 05, 2010 at 10:54:09AM -0700, Jesse Barnes wrote:
Longer answer: drm-intel-next bits are targeted at the next kernel
release. When important fixes from drm-intel-next land in Linus's tree,
you can request that they be back ported to the stable tree by sending a
note to
On Thu, Jul 29, 2010 at 10:58:53AM +1000, Dave Airlie wrote:
did this patch go anywhere?
It's now upstream in Linus's tree.
thanks,
greg k-h
On Mon, Jul 19, 2010 at 6:43 PM, Chris Wilson ch...@chris-wilson.co.uk
wrote:
From: Zhao Yakui yakui.z...@intel.com
When trying to set other
On Thu, Sep 29, 2011 at 06:09:32PM -0700, Keith Packard wrote:
Ok, so I've split all of the changes into bite-sized pieces so that
they should make sense individually now. I've also added the same
asynchronous power control to the panel power, this reduces the
module load time down to about
On Fri, Sep 30, 2011 at 01:58:29AM -0700, Keith Packard wrote:
On Thu, 29 Sep 2011 20:33:56 -0700, Greg KH g...@kroah.com wrote:
Are these really all -stable material?
I think just the sequence that actually makes the machine work; the
scarier patches are those which reduce the mode
On Fri, Aug 08, 2014 at 11:37:01AM +0200, Daniel Vetter wrote:
On Fri, Aug 08, 2014 at 10:20:40AM +0100, Chris Wilson wrote:
On Tue, Jul 29, 2014 at 12:26:36PM +0200, Daniel Vetter wrote:
On Tue, Jul 29, 2014 at 08:37:48AM +0100, Chris Wilson wrote:
On Mon, Jul 28, 2014 at 10:54:06AM
On Sun, Jun 09, 2013 at 11:18:16AM +0200, Daniel Vetter wrote:
Hi stable maintainers,
Please backport
commit e3de42b68478a8c95dd27520e9adead2af9477a5
Author: Imre Deak imre.d...@intel.com
Date: Fri May 3 19:44:07 2013 +0200
drm/i915: force full modeset if the connector is in DPMS
On Tue, Aug 06, 2013 at 08:57:35AM +0200, Daniel Vetter wrote:
This is the functional backport of upstream commit
09ede5414f0215461c933032630bf9c3a61a8ba3 Original commit message
below. Backport has been tested by the bug reporter, please consider
applying to all stable kernels.
We need to
has a bit
telling us not to look at the integrated PWM for the panel.
For 3.14 we will (again) resurrect the quirk because the vbt thing is a
bit too risky an imo needs a full -rc cycle for testing. But that revert
is currently stalled because Greg KH is travelling too much ;-)
Cc'ing him
On Wed, May 14, 2014 at 03:43:53PM -0400, Josh Boyer wrote:
On Wed, May 14, 2014 at 3:33 PM, Greg KH gre...@linuxfoundation.org wrote:
On Wed, May 14, 2014 at 09:19:32PM +0200, Daniel Vetter wrote:
On Wed, May 14, 2014 at 08:47:38PM +0200, Bruno Prémont wrote:
CCing intel-gfx as otherwise
On Wed, May 21, 2014 at 11:07:21AM +0200, Daniel Vetter wrote:
Hi Greg,
This is a set of drm/i915 patches which didn't apply cleanly on for 3.14. All
absed on 3.14.4. I've left out the bdw patches for now and will sign up
someone
else for that task.
Thanks for the patches, all now
On Tue, Dec 10, 2013 at 05:07:13PM +0200, ville.syrj...@linux.intel.com wrote:
Hi stable team,
Here's a backport of the following upstream commits for 3.12:
commit 662c6ecbcdca1fe8a5402f6c83d98d242917a043
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Wed Sep 25 14:24:01 2013 -0700
On Sun, Jan 26, 2014 at 01:11:15PM +0200, Imre Deak wrote:
On Sun, 2014-01-26 at 10:21 +0100, Daniel Vetter wrote:
On Sun, Jan 26, 2014 at 1:51 AM, Imre Deak imre.d...@intel.com wrote:
On Sat, 2014-01-25 at 21:37 +0100, Daniel Vetter wrote:
On Fri, Jan 24, 2014 at 02:47:33PM +0200, Imre
On Fri, Mar 21, 2014 at 03:14:48PM -0700, Ben Widawsky wrote:
On Fri, Mar 21, 2014 at 08:49:35PM +0100, Daniel Vetter wrote:
On Fri, Mar 21, 2014 at 7:48 PM, Ben Widawsky
benjamin.widaw...@linux.intel.com wrote:
The following patches are the backported simple fixes for 3.14. Some
of
On Mon, Mar 18, 2013 at 11:05:26AM +0100, Daniel Vetter wrote:
Hi Gregall,
So a recent stable backport to fix rc6 on ilk (which is disabled by
default and with dubious power savings at best, unlike rc6 on snb and
later) totally blew up all over the place:
On Fri, Apr 12, 2013 at 12:31:53AM -0700, Jonathan Nieder wrote:
Hi Greg,
Please consider
9a0f938bde74 drm/i915: Use the correct size of the GTT for placing
the per-process entries, 2012-08-24
for application to the 3.4.y tree.
Without this patch, Geoff Crompton's iMac
On Mon, May 06, 2013 at 10:36:49AM +0200, Daniel Vetter wrote:
On Mon, May 6, 2013 at 10:33 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote:
Dear stable team,
Please backport
commit 4615d4c9e27eda42c3e965f208a4b4065841498c
Author: Chris Wilson ch...@chris-wilson.co.uk
Date: Mon Apr
On Tue, Sep 17, 2013 at 01:13:26AM +0200, Daniel Vetter wrote:
Dear stable team,
Please packport the following upstream commit to 3.10:
commit 2960bc9cceecb5d556ce1c07656a66
09e2f7e8b0
Author: Imre Deak imre.d...@intel.com
Date: Tue Jul 30 13:36:32 2013 +0300
drm/i915: make user
On Sun, Oct 27, 2013 at 04:13:42PM +, Rob Pearce wrote:
From: Rob Pearce r...@flitspace.org.uk
The Intel D410PT(LW) and D425KT Mini-ITX desktop boards both show up as
having LVDS but the hardware is not populated. This patch adds them to
the list of such systems. Patch is against 3.11.4
Hi all,
I'm trying to the the $Subject laptop up and running using the built-in
Intel graphics chip:
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device 00f7
Flags:
On Tue, Jul 31, 2012 at 09:17:15AM +, Xu, Anhua wrote:
Thanks Chris. I add this in the the commit description. The updated patch is
below:
commit 71c3ff04834a01c81a5843996b87397273eb538d
Author: Xu Anhua anhua...@intel.com
Date: Tue Jul 31 17:16:50 2012 +0800
i915: make the
On Tue, Jul 31, 2012 at 03:00:52PM +1000, Dave Airlie wrote:
On Tue, Jul 31, 2012 at 1:41 PM, Greg KH gre...@linuxfoundation.org wrote:
On Tue, Jul 31, 2012 at 12:06:28PM +1000, Dave Airlie wrote:
On Tue, Jul 31, 2012 at 8:33 AM, Greg KH gre...@linuxfoundation.org
wrote:
Hi all
Hi Daniel.
The 3.6-rc1 kernel breaks my laptop, booting to a black screen when the
i915 driver initializes itself. I bisected this down to commit
24ded204429fa0f5501d37c63ee35c555c0b75ee (drm/i915: properly enable the
blc controller on the right pipe), and when I revert that, and also
On Sun, Aug 12, 2012 at 08:25:31PM +0200, Daniel Vetter wrote:
On Sun, Aug 12, 2012 at 11:21:57AM -0700, Greg KH wrote:
Hi Daniel.
The 3.6-rc1 kernel breaks my laptop, booting to a black screen when the
i915 driver initializes itself. I bisected this down to commit
On Sun, Aug 12, 2012 at 11:33:05AM -0700, Greg KH wrote:
On Sun, Aug 12, 2012 at 08:25:31PM +0200, Daniel Vetter wrote:
On Sun, Aug 12, 2012 at 11:21:57AM -0700, Greg KH wrote:
Hi Daniel.
The 3.6-rc1 kernel breaks my laptop, booting to a black screen when the
i915 driver
On Sat, Sep 22, 2012 at 07:52:11PM +0200, Daniel Vetter wrote:
Dave Airlie recently discovered a locking bug in the fbcon layer,
where a timer_del_sync (for the blinking cursor) deadlocks with the
timer itself, since both (want to) hold the console_lock:
https://lkml.org/lkml/2012/8/21/36
On Tue, Oct 02, 2012 at 02:56:48PM +0200, Daniel Vetter wrote:
On Sat, Sep 22, 2012 at 10:06 PM, Greg KH gre...@linuxfoundation.org wrote:
On Sat, Sep 22, 2012 at 07:52:11PM +0200, Daniel Vetter wrote:
Dave Airlie recently discovered a locking bug in the fbcon layer,
where a timer_del_sync
On Mon, Oct 15, 2012 at 10:11:22AM +0200, Daniel Vetter wrote:
Hi Gregstable-team,
The below patch papers over a graphics corruption issue in 3.5/3.6. The
regression happened due to pwrite tunings in 3.5, which made cpu relocations
much more likely.
The issue seems to have disappeared in
On Mon, Oct 15, 2012 at 07:16:26PM +0200, Daniel Vetter wrote:
On Mon, Oct 15, 2012 at 5:11 PM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Oct 15, 2012 at 10:11:22AM +0200, Daniel Vetter wrote:
Hi Gregstable-team,
The below patch papers over a graphics corruption issue in 3.5/3.6
On Sun, Oct 21, 2012 at 12:41:35PM -0700, Jonathan Nieder wrote:
Hi Ben and Greg,
Please consider
9756fe38d10b drm/i915: no lvds quirk for Zotac ZDBOX SD ID12/ID13
for application to the 3.0.y, 3.2.y, and 3.4.y trees. It was applied
upstream during the 3.6 merge window, so newer
Hi all,
I've hit this 3 times today on Linus's latest 3.8-rc2+ tree:
[11868.414648] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU
hung
[11868.414655] [drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[11870.408342]
On Wed, Jan 09, 2013 at 01:42:39PM +1000, Dave Airlie wrote:
Hi all,
I've hit this 3 times today on Linus's latest 3.8-rc2+ tree:
[11868.414648] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer
elapsed... GPU hung
[11868.414655] [drm] capturing error event; look for more
On Wed, Jan 09, 2013 at 02:12:04PM -0600, Dave Kleikamp wrote:
On 01/09/2013 01:44 PM, Dave Kleikamp wrote:
I can easily reproduce it running glxgears on 3.8-rc1 or 3.8-rc2.
00:02.0 VGA compatible controller [0300]: Intel Corporation Core
Processor Integrated Graphics Controller
On Wed, Jan 09, 2013 at 02:12:04PM -0600, Dave Kleikamp wrote:
On 01/09/2013 01:44 PM, Dave Kleikamp wrote:
I can easily reproduce it running glxgears on 3.8-rc1 or 3.8-rc2.
00:02.0 VGA compatible controller [0300]: Intel Corporation Core
Processor Integrated Graphics Controller
On Thu, Mar 26, 2015 at 05:40:07PM -0400, Josh Boyer wrote:
On Mon, Mar 2, 2015 at 4:30 AM, Jani Nikula jani.nik...@intel.com wrote:
Stable team, please backport
commit f9b61ff6bce9a44555324b29e593fdffc9a115bc
Author: Daniel Vetter daniel.vet...@ffwll.ch
Date: Wed Jan 7 13:54:39
On Thu, May 07, 2015 at 01:00:52PM +0530, Sumit Semwal wrote:
Add reference counting on a kernel module that exports dma-buf and
implements its operations. This prevents the module from being unloaded
while DMABUF file is in use.
The original patch [1] was submitted by Tomasz, but he's since
On Mon, May 11, 2015 at 12:05:27PM +0100, Peter Antoine wrote:
This patch fixed a timing issue that causes a GPU hang when a the system
comes out of power saving.
During pm_resume, We are submitting batchbuffers before enabling
Interrupts this is causing us to miss the context switch
now until we've had a decent
discussion with Greg KH (since imo his stance of every driver creating
it's own retry loop just doesn't work, especially not with gfx where init
is hairy and you just don't want to retry without end).
Exactly, this type of thing isn't good at all (especially given
On Mon, Oct 19, 2015 at 11:02:35AM +0300, Jani Nikula wrote:
> On Sat, 17 Oct 2015, Greg KH <gre...@linuxfoundation.org> wrote:
> > On Mon, Sep 28, 2015 at 10:09:11PM +0300, ville.syrj...@linux.intel.com
> > wrote:
> >> From: Ville Syrjälä <ville.syrj...@l
On Mon, Sep 28, 2015 at 10:09:11PM +0300, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> commit 58590c14d80defc94e900308a9d8fa55284de6f2 upstream.
This is not the commit id of the patch below at all, I can't take this,
please be more careful in the
On Mon, Oct 19, 2015 at 06:10:39PM +0200, Daniel Vetter wrote:
> On Mon, Oct 19, 2015 at 08:13:05AM -0700, Greg KH wrote:
> > On Mon, Oct 19, 2015 at 11:02:35AM +0300, Jani Nikula wrote:
> > > On Sat, 17 Oct 2015, Greg KH <gre...@linuxfoundation.org> wrote:
> > >
On Fri, May 27, 2016 at 11:30:30AM +0300, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> Several nasty i915 regressions affecting CHV slipped through
> to 4.5 and 4.6.
>
> The first fix we want in 4.5 and 4.6 is
> commit caed361d83b2 ("drm/i915:
On Wed, Jun 22, 2016 at 03:55:03PM +0200, Daniel Vetter wrote:
> On Mon, Jun 6, 2016 at 11:32 AM, Ville Syrjälä
> <ville.syrj...@linux.intel.com> wrote:
> > On Sat, Jun 04, 2016 at 02:06:58PM -0700, Greg KH wrote:
> >> On Fri, May 27, 2016 at 11:30:30AM +0300, vi
On Mon, Aug 22, 2016 at 11:31:31AM -0400, Lyude wrote:
> Hope this didn't take too long! Here's the backported versions of the patches
> you had trouble applying to stable. The patch for FBC won't be necessary as
> that is already present in 4.7.y.
>
> Cheers,
> Lyude
Thanks, but what are
On Mon, Aug 29, 2016 at 05:27:38PM -0400, Lyude Paul wrote:
> drm/i915/vlv: Make intel_crt_reset() per-encoder:
> 4570d833390b10043d082fe535375d4a0e071d9c
> drm/i915/vlv: Reset the ADPA in vlv_display_power_well_init():
> 4c732e6ee9e71903934d75b12a021eb3520b6197
> drm/i915/vlv: Disable HPD in
On Thu, Sep 15, 2016 at 11:12:08AM +0800, bobcao3 wrote:
> Signed-off-by: bobcao3
> ---
> drivers/gpu/drm/i915/i915_gem_gtt.c | 6
> drivers/gpu/drm/i915/i915_gem_stolen.c | 61
> -
> drivers/gpu/drm/i915/i915_reg.h | 6
On Fri, Oct 07, 2016 at 10:38:17AM -0300, Gaston Gonzalez wrote:
> On Wed, Oct 05, 2016 at 07:23:23AM +0200, Greg KH wrote:
> > On Tue, Oct 04, 2016 at 08:43:03PM -0300, Gaston Gonzalez wrote:
> > > Hi,
> > >
> > > After hibernation I get the fol
On Sat, Oct 29, 2016 at 10:13:25AM -0300, Gaston Gonzalez wrote:
> On Fri, Oct 28, 2016 at 07:23:24PM +0300, Ville Syrjälä wrote:
> > On Fri, Oct 28, 2016 at 11:53:40AM -0400, Greg KH wrote:
> > > On Fri, Oct 07, 2016 at 10:38:17AM -0300, Gaston Gonzalez wrote:
> > > &
On Wed, Oct 26, 2016 at 03:36:32PM -0400, Lyude wrote:
> Now that these have finally made it into 4.9, it's time to finally backport
> these fixes. Skylake has been a mess in multi-monitor setups for a while now
> because up until recently we've been updating the watermarks on Skylake just
> like
On Tue, Oct 11, 2016 at 01:54:09PM +0300, Jani Nikula wrote:
> On Tue, 11 Oct 2016, Greg KH <g...@kroah.com> wrote:
> > On Tue, Oct 11, 2016 at 10:34:14AM +0300, Jani Nikula wrote:
> >> On Mon, 10 Oct 2016, Paulo Zanoni <paulo.r.zan...@intel.com> wrote:
> >&g
On Tue, Oct 11, 2016 at 10:34:14AM +0300, Jani Nikula wrote:
> On Mon, 10 Oct 2016, Paulo Zanoni wrote:
> > Mahesh Kumar is already working on a proper implementation for the
> > workaround, but while we still don't have it, let's just
> > unconditionally apply the
On Thu, Mar 16, 2017 at 08:38:30AM +0100, Daniel Vetter wrote:
> Hi Greg,
>
> On Mon, Mar 13, 2017 at 07:40:50AM +0100, Daniel Vetter wrote:
> > On Sun, Mar 12, 2017 at 11:01 PM, Greg KH <gre...@linuxfoundation.org>
> > wrote:
> > > So if a commit says "
On Thu, Mar 16, 2017 at 04:40:01PM +0200, Jani Nikula wrote:
> On Thu, 16 Mar 2017, Greg KH <gre...@linuxfoundation.org> wrote:
> > And again, you all are the only ones that have this issue. You might
> > find a handfull of patches for stable that come in twice in the r
On Mon, Mar 13, 2017 at 07:49:59AM +0100, Daniel Vetter wrote:
> On Sun, Mar 12, 2017 at 10:52 PM, Greg KH <gre...@linuxfoundation.org> wrote:
> > Why don't the maintainers know which tree to put them in when they are
> > submitted? As an example, if I get a patch that ne
On Wed, Apr 12, 2017 at 02:48:55PM +0200, Greg KH wrote:
> On Mon, Mar 13, 2017 at 07:49:59AM +0100, Daniel Vetter wrote:
> > On Sun, Mar 12, 2017 at 10:52 PM, Greg KH <gre...@linuxfoundation.org>
> > wrote:
> > > Why don't the maintainers know
Hi Daniel and Jani and other members of the i915-commit-cabal,
I've mentioned this a few times to Daniel in the past (like at the last
kernel summit), but the way you all are handling the tagging of patches
for inclusion in stable kernel releases is totally broken and causing me
no end of
On Mon, Mar 13, 2017 at 06:11:12AM +1000, Dave Airlie wrote:
> On 13 March 2017 at 05:44, Greg KH <gre...@linuxfoundation.org> wrote:
> > Hi Daniel and Jani and other members of the i915-commit-cabal,
> >
> > I've mentioned this a few times to Daniel in the past (like at
On Sun, Mar 12, 2017 at 09:46:21PM +0100, Daniel Vetter wrote:
> On Sun, Mar 12, 2017 at 08:44:40PM +0100, Greg KH wrote:
> > Hi Daniel and Jani and other members of the i915-commit-cabal,
> >
> > I've mentioned this a few times to Daniel in the past (like at the l
On Mon, Jul 24, 2017 at 10:24:41AM +0200, Daniel Vetter wrote:
> On Mon, Jul 24, 2017 at 2:03 AM, Stephen Rothwell
> wrote:
> > Hi Daniel,
> >
> > On Fri, 21 Jul 2017 09:24:49 +0200 Daniel Vetter
> > wrote:
> >>
> >> How are we going to handle
On Fri, May 26, 2017 at 02:21:10PM +0300, Jani Nikula wrote:
>
> Stable team, please backport upstream commits
>
> 665788572c64 ("drm/i915/vbt: don't propagate errors from intel_bios_init()")
> bb1d132935c2 ("drm/i915/vbt: split out defaults that are set when there is no
> VBT")
>
> to stable
On Thu, Jun 15, 2017 at 08:51:34AM +0300, Jani Nikula wrote:
> On Wed, 14 Jun 2017, Eric Blau wrote:
> > Can the following patch please be included in the next stable release?
> > It looks like it was submitted previously by Daniel Vetter, but has not
> > been included in 4.11.y
On Thu, Jun 15, 2017 at 09:55:45AM +0300, Jani Nikula wrote:
> On Thu, 15 Jun 2017, Greg KH <gre...@linuxfoundation.org> wrote:
> > Ugh, this one flew right by me, and I never even caught it. And that
> > was because it was sent To: the intel-gfx list, and only had a cc: for
On Sun, Oct 01, 2017 at 08:52:20PM -0400, Jérémy Lefaure wrote:
> On Mon, 2 Oct 2017 09:01:31 +1100
> "Tobin C. Harding" wrote:
>
> > > In order to reduce the size of the To: and Cc: lines, each patch of the
> > > series is sent only to the maintainers and lists concerned by the
On Thu, Nov 23, 2017 at 10:09:25PM +0100, Rainer Fiebig wrote:
> Rainer Fiebig wrote:
> > Maarten Lankhorst wrote:
> >> Op 20-11-17 om 09:51 schreef Rainer Fiebig:
> >>> Jani Nikula wrote:
> >>>> On Sun, 19 Nov 2017, Greg KH <gre...@linuxfoundation.o
On Fri, Nov 24, 2017 at 07:48:22AM +0100, Greg KH wrote:
> On Thu, Nov 23, 2017 at 10:09:25PM +0100, Rainer Fiebig wrote:
> > Rainer Fiebig wrote:
> > > Maarten Lankhorst wrote:
> > >> Op 20-11-17 om 09:51 schreef Rainer Fiebig:
> > >>> Jani Nikula wrot
On Fri, Nov 17, 2017 at 02:53:43PM +0200, Ville Syrjälä wrote:
> On Fri, Nov 17, 2017 at 01:41:23PM +0100, Greg KH wrote:
> > On Fri, Nov 17, 2017 at 01:28:05PM +0200, Jani Nikula wrote:
> > >
> > > Cc: Greg
> > >
> > > On Wed, 15 Nov 2017, Ville
On Fri, Nov 17, 2017 at 01:28:05PM +0200, Jani Nikula wrote:
>
> Cc: Greg
>
> On Wed, 15 Nov 2017, Ville Syrjälä wrote:
> > On Wed, Nov 15, 2017 at 04:44:54PM +, alexander.le...@verizon.com wrote:
> >> On Wed, Nov 15, 2017 at 01:08:05PM +0200, Ville Syrjälä
On Fri, Nov 17, 2017 at 03:01:08PM +0200, Jani Nikula wrote:
> On Fri, 17 Nov 2017, Greg KH <gre...@linuxfoundation.org> wrote:
> > On Fri, Nov 17, 2017 at 01:28:05PM +0200, Jani Nikula wrote:
> >>
> >> Cc: Greg
> >>
> >> On Wed, 15 Nov 2017,
On Fri, Nov 17, 2017 at 01:13:27PM +, Emil Velikov wrote:
> Hi Greg, all,
>
> Pardon for the silly question, but I'm struggling to find
> documentation about this new 'autoselection' process?
> Where can one read up on it - be that about the tooling or the heuristics
> used?
>
> I think the
On Mon, Nov 20, 2017 at 01:39:31PM +0100, Daniel Vetter wrote:
> Of course our CI is open, so if someone is supremely bored and wants to
> backport more stuff for drm/i915, they could do that. But atm it doesn't
> happen, and then having to deal with the fallout is not really great (like
> I said,
On Sun, Nov 19, 2017 at 01:44:06PM +0100, Rainer Fiebig wrote:
> Greg KH wrote:
> > On Sun, Nov 19, 2017 at 12:56:26PM +0100, Rainer Fiebig wrote:
> >> Greg KH wrote:
> >>> On Sat, Nov 18, 2017 at 05:08:20PM +0100, Rainer Fiebig wrote:
> >>>> Greg KH
On Sun, Nov 19, 2017 at 12:56:26PM +0100, Rainer Fiebig wrote:
> Greg KH wrote:
> > On Sat, Nov 18, 2017 at 05:08:20PM +0100, Rainer Fiebig wrote:
> >> Greg KH wrote:
> >>> On Sat, Nov 18, 2017 at 01:47:32PM +0100, Rainer Fiebig wrote:
> >>>> Hi
On Tue, Nov 21, 2017 at 12:09:33PM -0500, Josh Boyer wrote:
> On Tue, Nov 21, 2017 at 10:07 AM, wrote:
> > On Mon, Nov 20, 2017 at 11:21:52AM +, Emil Velikov wrote:
> >> - Document the autoselect process
> >>Information about about What, Why, and [ideally] How -
On Fri, Feb 02, 2018 at 12:44:38PM +0200, Jani Nikula wrote:
>
> +Knut, Fengguang
>
> On Fri, 02 Feb 2018, Greg KH <gre...@linuxfoundation.org> wrote:
> > - If clang now builds the kernel "cleanly", yes, I want to take
> > warning fixes in the s
On Fri, Feb 02, 2018 at 04:37:55PM +0200, Jani Nikula wrote:
> On Fri, 02 Feb 2018, Greg KH <gre...@linuxfoundation.org> wrote:
> > On Fri, Feb 02, 2018 at 12:44:38PM +0200, Jani Nikula wrote:
> >>
> >> +Knut, Fengguang
> >>
> >> On Fri, 02 F
On Thu, Feb 01, 2018 at 06:33:30PM +0100, Ozan Alpay wrote:
> Dear Rodrigo Vivi, Ville Syrjälä,
>
> My name is Ozan Alpay, and I am a student mentored by Lukas Bulwahn. We
> intend to use static analysis tools on the kernel source to identify,
> analyze and report issues. As a very first step,
On Fri, Feb 02, 2018 at 10:56:36AM +0100, Lukas Bulwahn wrote:
> On Fri, 2 Feb 2018, Jani Nikula wrote:
>
> > Being brutally honest, please write shorter reports and shorter emails
> > to the lists.
> >
> > The static analysis reports are welcome, but only when 1) we didn't
> > already fix it in
On Thu, Feb 01, 2018 at 06:48:30PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> These backports fix a plane related regression causing a corrupted
> screen and bunch of WARNs from the kernel on some pre-i965 era
> hardware.
>
> Cc:
On Wed, Feb 14, 2018 at 06:22:56PM +0200, Jani Nikula wrote:
>
> Stable team,
>
> commit 9965db26ac05 ("drm/i915: Check for fused or unused pipes")
>
> with Cc: stable is broken, please do not backport.
Ok, now dropped from my "to-apply" queue, thanks.
greg k-h
On Fri, Mar 02, 2018 at 11:29:14AM +0200, Jani Nikula wrote:
> On Thu, 15 Feb 2018, Greg KH <g...@kroah.com> wrote:
> > On Wed, Feb 14, 2018 at 06:22:56PM +0200, Jani Nikula wrote:
> >>
> >> Stable team,
> >>
> >> commit 9965d
On Mon, Mar 12, 2018 at 02:06:50PM +, Lionel Landwerlin wrote:
> This is a backport of commit f616f2830c1ed79245cfeca900f7e8a3b3c08c06
> sent for fixes on 4.14+ (but didn't apply cleanly on linux-4.14.y,
> linux-4.15.y). This upstream commit for this change is
>
On Mon, Mar 12, 2018 at 03:34:57PM -0700, Rodrigo Vivi wrote:
> From: Anusha Srivatsa
>
> commit 2afba81c7909ac259720c0d3e7616cf54d4a5368 upstream.
>
> Since the firmwares are not yet released to public repo,
> disable them on Geminilake.
>
> v2: Remove the firmware
On Tue, Apr 03, 2018 at 10:27:16AM +0300, Jani Nikula wrote:
>
> DK, please start stable backport commit messages with:
>
> commit b1e314462bba76660eec62760bb2e87f28f58866 upstream.
Thank you for that, it helped me figure this out...
greg k-h
___
On Wed, Jan 23, 2019 at 03:03:47AM -0800, Kees Cook wrote:
> Variables declared in a switch statement before any case statements
> cannot be initialized, so move all instances out of the switches.
> After this, future always-initialized stack variables will work
> and not throw warnings like this:
On Thu, Nov 29, 2018 at 01:09:21PM +0200, Stanislav Lisovskiy wrote:
> Currently kernel might allocate different connector ids
> for the same outputs in case of DP MST, which seems to
> confuse userspace. There are can be different connector
> ids in the list, which could be assigned to the same
>
On Wed, Sep 12, 2018 at 04:59:10PM +0300, Jani Nikula wrote:
> commit 6209c285e7a5e68dbcdf8fd2456c6dd68433806b upstream.
Thanks for the backport, now queued up.
greg k-h
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
On Fri, Sep 14, 2018 at 04:39:42PM +0300, Jani Nikula wrote:
> commit 6209c285e7a5e68dbcdf8fd2456c6dd68433806b upstream.
Now applied, thanks.
greg k-h
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
On Tue, Feb 26, 2019 at 10:17:10PM +0100, Daniel Vetter wrote:
> Hi Greg
>
> topic/mei-hdcp-2019-02-26:
> mei-hdcp driver
>
> mei driver for the me hdcp client, for use by drm/i915.
>
> Including the following prep work:
> - whitelist hdcp client in mei bus
> - merge to include char-misc-next
On Tue, Feb 19, 2019 at 08:55:27AM +0100, Daniel Vetter wrote:
> Hi all,
>
> topic/mei-hdcp-2019-02-19:
> Prep patches + headers for the mei-hdcp/i915 component interfaces
>
> Also contains the prep work in the component helpers plus adjustements
> for the snd-hda/i915 component interface.
>
>
On Mon, Feb 11, 2019 at 08:18:04PM +0100, Daniel Vetter wrote:
> On Mon, Feb 11, 2019 at 7:57 PM Takashi Iwai wrote:
> >
> > On Mon, 11 Feb 2019 19:25:12 +0100,
> > Sam Ravnborg wrote:
> > >
> > > Hi Daniel.
> > >
> > > On Mon, Feb 11, 2019 at 06:15:20PM +0100, Daniel Vetter wrote:
> > > > Hi
On Sat, Feb 09, 2019 at 12:42:50PM +0530, Ramalingam C wrote:
> From: Tomas Winkler
>
> Add icelake mei device id.
>
> Cc:
> Signed-off-by: Tomas Winkler
> Signed-off-by: Greg Kroah-Hartman
> Cherry-picked from
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
>
On Thu, Jan 24, 2019 at 07:55:51AM +1300, Kees Cook wrote:
> On Thu, Jan 24, 2019 at 4:44 AM Jani Nikula
> wrote:
> >
> > On Wed, 23 Jan 2019, Edwin Zimmerman wrote:
> > > On Wed, 23 Jan 2019, Jani Nikula wrote:
> > >> On Wed, 23 Jan 2019, Greg KH wrote:
On Mon, Apr 15, 2019 at 03:58:37PM +0300, Jani Nikula wrote:
> commit 21635d7311734d2d1b177f8a95e2f9386174b76d upstream.
>
> Commit 7769db588384 ("drm/i915/dp: optimize eDP 1.4+ link config fast
> and narrow") started to optize the eDP 1.4+ link config, both per spec
> and as preparation for
On Mon, May 27, 2019 at 09:11:26AM +0200, Daniel Vetter wrote:
> On Fri, May 24, 2019 at 10:53:53AM +0200, Daniel Vetter wrote:
> > this driver is pretty horrible from a design pov, and needs a complete
> > overhaul. Concrete thing that annoys me is that it looks at
> > registered_fb, which is an
On Mon, May 27, 2019 at 09:10:10AM +0200, Daniel Vetter wrote:
> On Fri, May 24, 2019 at 10:53:35AM +0200, Daniel Vetter wrote:
> > Simply because olpc never unregisters the damn thing. It also
> > registers the framebuffer directly by poking around in fbdev
> > core internals, so it's all around
On Fri, Jun 14, 2019 at 04:48:57PM +0200, Christoph Hellwig wrote:
> On Fri, Jun 14, 2019 at 04:02:39PM +0200, Greg KH wrote:
> > Perhaps a hint as to how we can fix this up? This is the first time
> > I've heard of the comedi code not handling dma properly.
>
On Fri, Jun 14, 2019 at 03:47:22PM +0200, Christoph Hellwig wrote:
> comedi_buf.c abuse the DMA API in gravely broken ways, as it assumes it
> can call virt_to_page on the result, and the just remap it as uncached
> using vmap. Disable the driver until this API abuse has been fixed.
>
>
On Wed, May 08, 2019 at 04:11:28PM +0300, Andy Shevchenko wrote:
> On Wed, May 08, 2019 at 02:28:29PM +0300, Alexandru Ardelean wrote:
> > This change re-introduces `match_string()` as a macro that uses
> > ARRAY_SIZE() to compute the size of the array.
> > The macro is added in all the places
On Tue, Jul 02, 2019 at 12:23:04PM -0700, Lucas De Marchi wrote:
> commit bc7b488b1d1c71dc4c5182206911127bc6c410d6 upstream.
>
> While loading the DMC firmware we were double checking the headers made
> sense, but in no place we checked that we were actually reading memory
> we were supposed to.
On Tue, Sep 03, 2019 at 02:55:26PM +0800, Baolin Wang wrote:
> From: Chris Wilson
>
> If we skipped all the connectors that were not part of a tile, we would
> leave conn_seq=0 and conn_configured=0, convincing ourselves that we
> had stagnated in our configuration attempts. Avoid this situation
On Tue, Jul 30, 2019 at 08:19:08AM -0700, Rodrigo Vivi wrote:
> Hi Greg,
>
> On Wed, Jul 24, 2019 at 10:40:29AM -0700, Rodrigo Vivi wrote:
> > On Wed, Jul 24, 2019 at 05:27:42PM +, Souza, Jose wrote:
> > > On Wed, 2019-07-24 at 14:06 +0200, Greg KH wrote:
> > >
1 - 100 of 187 matches
Mail list logo