linux-kernel - Re: [git pull] drm merge tree

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]

Date:	Thu, 12 Jun 2014 12:06:53 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Airlie <airlied@...ux.ie>,
	Daniel Vetter <daniel.vetter@...ll.ch>
Cc:	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm merge tree

On Wed, Jun 11, 2014 at 5:58 PM, Dave Airlie <airlied@...ux.ie> wrote:
>
> This is the main drm merge window pull request, changes all over the place, mostly normal levels of churn.

Hmm.

I just had the machine reboot on me when booting this and starting X,
leaving nothing in the logs.

This is on a bog-standard i7-4770S setup (so Haswell with Intel
integrated graphics).

I'm going to test it a few more times, but if I can recreate it, I'm
going to unpull this and that will basically mean that since it came
in late in the merge window, the whole thing will miss 3.16.

Because there is no way I will release an rc1 that just doesn't work
on my main machine. I'm ok with fixing bugs after-the-fact, but bugs
that cause my own machine to be unstable? That just means I won't
pull.

This is just a heads-up, I will have to see how bad this is.

              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/