From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
Chris Wilson <chris@chris-wilson.co.uk>,
Keith Packard <keithp@keithp.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] drm next tree
Date: Wed, 23 Mar 2011 08:33:29 -0700 [thread overview]
Message-ID: <20110323083329.64a738c6@jbarnes-desktop> (raw)
In-Reply-To: <AANLkTi=zcXFOGj+pi1YSVY1kHoULEAQRNrnzmw2Pexns@mail.gmail.com>
On Wed, 23 Mar 2011 08:29:35 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Tue, Mar 22, 2011 at 7:19 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Keith/Jesse/Chris - I don't know that it's i915, and it will take
> > forever to bisect (I'll try). But it does seem pretty likely.
>
> Ok, so I'm still bisecting, but it's definitely the DRM pull. Current
> bisection log attached (the result does contain the fbdev pull from
> Paul Mundt, but that doesn't touch any files I compile afaik).
Chris mentioned a7a75c8f7 on irc, not sure if it was regarding this
issue though, but it does seem a likely candidate.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-03-23 15:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 4:09 [git pull] drm next tree Dave Airlie
2011-03-23 2:19 ` Linus Torvalds
2011-03-23 12:21 ` Stephen Clark
2011-03-23 14:39 ` Jerome Glisse
2011-03-23 15:22 ` Jesse Barnes
2011-03-23 14:22 ` Alessandro Suardi
2011-03-23 15:29 ` Linus Torvalds
2011-03-23 15:33 ` Jesse Barnes [this message]
2011-03-24 0:54 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2014-01-30 2:49 Dave Airlie
2014-01-30 4:54 ` Linus Torvalds
2014-01-30 12:33 ` Paul Bolle
2014-01-30 15:55 ` Jiri Kosina
2014-02-07 10:08 ` Jiri Kosina
2014-02-07 11:10 ` Jani Nikula
2014-02-07 13:40 ` Jiri Kosina
2014-02-07 14:05 ` Daniel Vetter
2014-02-07 14:15 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110323083329.64a738c6@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox