linux-kernel - Re: [git pull] drm fixes

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFxTAHTXRmnK9AeJm525u28SGRxCRMAvY8rJcNuwkHANtg@mail.gmail.com>
Date:	Wed, 25 Jan 2012 15:31:24 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Airlie <airlied@...ux.ie>
Cc:	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [git pull] drm fixes

On Wed, Jan 25, 2012 at 11:05 AM, Dave Airlie <airlied@...ux.ie> wrote:
>
> bunch of regression fixes since TTM rework and radeon initialisation,
> modesetting fixes for Alex to fix some black screens on kms start type
> issues, and two radeon ACPI fixes that make some laptops no oops on
> startup.

Does that include for the nvidia (?) suspend/resume issue? You were
cc'd on it (but the subject may have made you ignore it - it was part
of a thread about wireless network suspend issues: "bcma/brcmsmac
suspend/resume cleanups and fixes"):

  No trivial bisect. I wish I had a faster build machine, but alas. I
  suspected some issue in DRM and the bisect took me into drm-core-next
  branch. I ended up at the following commit:

  dc97b3409a790d2a21aac6e5cdb99558b5944119 is the first bad commit
  commit dc97b3409a790d2a21aac6e5cdb99558b5944119
  Author: Jerome Glisse <jglisse@...hat.com>
  Date:   Fri Nov 18 11:47:03 2011 -0500

Hmm?

                     Linus
--
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/