From: Daniel Vetter <daniel@ffwll.ch>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Daniel Vetter <daniel@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Excessive WARN()s in Intel 915 driver
Date: Mon, 27 Jan 2014 16:56:40 +0100 [thread overview]
Message-ID: <20140127155640.GA9772@phenom.ffwll.local> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1401271024570.1207-100000@iolanthe.rowland.org>
On Mon, Jan 27, 2014 at 10:30:11AM -0500, Alan Stern wrote:
> On Mon, 27 Jan 2014, Daniel Vetter wrote:
>
> > On Tue, Jan 14, 2014 at 3:43 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> > > Don't bother. I'll redo it using the drm-intel-nightly branch, but I
> > > won't have time for a few days.
> >
> > My apologies for the delay in getting around to this. Can you please
> > test the patch i've just posted?
> >
> > http://patchwork.freedesktop.org/patch/18810/
>
> I will.
>
> By the way, I tried getting an up-to-date version of your
> drm-intel-nightly branch, and ended up with the following:
>
> $ git clone --depth 1 -b drm-intel-nightly http://cgit.freedesktop.org/~danvet/drm-intel/
> Cloning into 'drm-intel'...
> fatal: dumb http transport does not support --depth
>
> (I can't remember what happened the first time I tried to clone your
> repository). So I will try running with this patch on top of 3.13.
Well, use the git:// link with --depth ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-01-27 15:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 18:50 Excessive WARN()s in Intel 915 driver Alan Stern
2014-01-07 20:12 ` Daniel Vetter
2014-01-08 16:08 ` Alan Stern
2014-01-08 16:17 ` Daniel Vetter
2014-01-08 18:34 ` Alan Stern
2014-01-08 20:21 ` Daniel Vetter
2014-01-08 20:21 ` Daniel Vetter
2014-01-08 23:15 ` Alan Stern
2014-01-13 20:16 ` Alan Stern
2014-01-14 9:05 ` Daniel Vetter
2014-01-14 14:43 ` Alan Stern
2014-01-27 9:02 ` Daniel Vetter
2014-01-27 15:30 ` Alan Stern
2014-01-27 15:56 ` Daniel Vetter [this message]
2014-01-27 16:05 ` Alan Stern
2014-01-27 16:36 ` Daniel Vetter
2014-01-27 16:36 ` Daniel Vetter
2014-01-27 17:14 ` Alan Stern
2014-01-28 16:34 ` Alan Stern
2014-01-28 16:34 ` Alan Stern
2014-01-14 12:52 ` [Intel-gfx] " Jani Nikula
2014-01-08 18:43 ` Ville Syrjälä
2014-01-08 18:43 ` Ville Syrjälä
2014-01-28 17:17 ` [Intel-gfx] " Daniel Vetter
2014-01-28 17:17 ` Daniel Vetter
2014-01-28 19:42 ` [Intel-gfx] " Daniel Vetter
2014-01-28 19:42 ` Daniel Vetter
2014-01-30 14:53 ` [Intel-gfx] " Alan Stern
2014-01-30 14:53 ` Alan Stern
2014-01-30 15:22 ` [Intel-gfx] " Daniel Vetter
2014-01-30 15:22 ` Daniel Vetter
2014-01-30 15:52 ` [Intel-gfx] " Alan Stern
2014-01-30 15:52 ` Alan Stern
2014-06-25 18:06 ` Regression in i915 driver in 3.16-rc2 Alan Stern
2014-06-25 18:26 ` [Intel-gfx] " Ville Syrjälä
2014-06-25 18:26 ` Ville Syrjälä
2014-06-25 18:50 ` [Intel-gfx] " Alan Stern
2014-06-25 18:50 ` Alan Stern
2014-06-30 10:52 ` [Intel-gfx] " Jani Nikula
2014-06-30 10:52 ` Jani Nikula
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=20140127155640.GA9772@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.