From: Daniel Vetter <daniel@ffwll•ch>
To: Sedat Dilek <sedat.dilek@gmail•com>
Cc: Daniel Vetter <daniel.vetter@ffwll•ch>,
Chris Wilson <chris@chris-wilson•co.uk>,
linux-next <linux-next@vger•kernel.org>,
LKML <linux-kernel@vger•kernel.org>,
intel-gfx <intel-gfx@lists•freedesktop.org>,
Stephen Rothwell <sfr@canb•auug.org.au>
Subject: Re: linux-next: Tree for Aug 21 [ screen corruption in graphical mode ]
Date: Wed, 21 Aug 2013 15:44:41 +0200 [thread overview]
Message-ID: <20130821134441.GE26909@phenom.ffwll.local> (raw)
In-Reply-To: <CA+icZUUkS-UptLRM1CfcaHH=8UD-ZaHbXr8wFkA+YKyk-rPjvg@mail.gmail.com>
On Wed, Aug 21, 2013 at 12:35:08PM +0200, Sedat Dilek wrote:
> On Wed, Aug 21, 2013 at 11:21 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > Hi all,
> >
> > There will be no linux-next trees on Aug 23 or 26.
> >
> > Changes since 20130820:
> >
> > New tree: aio-direct
> >
> > Removed tree: xilinx (at maintainer's request)
> >
> > The xfs tree still had its build failure for which I reverted a commit.
> >
> > The trivial tree gained conflicts against the crypto, net-next and
> > wireless trees.
> >
> > The aio tree gained conflicts against the aio-direct tree.
> >
> > The akpm-current tree gained conflicts against the modules and aio-direct
> > trees.
> >
> > ----------------------------------------------------------------------------
> >
>
> Hi,
>
> I still have this issue with next-20130821 and "Linux v3.11-rc6 plus
> drm-intel-nightly on top"
> Any new development on this?
> Patches?
Tbh I'm at a loss what we could try above&beyond what Chris has already
tried out.
> Currently, I have two workarounds:
>
> [1] Revert this commit:
>
> commit 5456fe3882812aba251886e36fe55bfefb8e8829
> "drm/i915: Allocate LLC ringbuffers from stolen"
Since with a rather decent chance the next testing cycle I'll do this
friday will be the last chunk of features for 3.12 I'll probably drop the
above patch from my queue and we can try again in 3.13.
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-08-21 13:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 10:35 linux-next: Tree for Aug 21 [ screen corruption in graphical mode ] Sedat Dilek
2013-08-21 13:44 ` Daniel Vetter [this message]
2013-08-21 18:11 ` Sedat Dilek
2013-08-21 21:20 ` Daniel Vetter
2013-08-22 6:32 ` Sedat Dilek
2013-08-22 7:24 ` Daniel Vetter
2013-08-22 11:13 ` Sedat Dilek
2013-08-22 11:22 ` Sedat Dilek
2013-08-22 11:30 ` Daniel Vetter
2013-08-22 11:32 ` Daniel Vetter
2013-08-23 7:55 ` Sedat Dilek
2013-08-23 8:04 ` Sedat Dilek
2013-08-23 8:34 ` Chris Wilson
2013-08-23 8:47 ` Sedat Dilek
2013-08-24 9:35 ` Sedat Dilek
2013-08-24 10:55 ` Sedat Dilek
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=20130821134441.GE26909@phenom.ffwll.local \
--to=daniel@ffwll$(echo .)ch \
--cc=chris@chris-wilson$(echo .)co.uk \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sedat.dilek@gmail$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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