From: Peter Zijlstra <peterz@infradead.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"pasha.tatashin@oracle.com" <pasha.tatashin@oracle.com>,
"Peres, Martin" <martin.peres@intel.com>
Subject: Re: freedesktop bug id: 100548, bisected to sched/clock commit
Date: Wed, 12 Apr 2017 16:28:09 +0200 [thread overview]
Message-ID: <20170412142809.awtdkxr4fguivjkz@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <87y3v5wy6f.fsf@intel.com>
On Wed, Apr 12, 2017 at 04:30:32PM +0300, Jani Nikula wrote:
> On Wed, 12 Apr 2017, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Wed, Apr 12, 2017 at 12:04:00PM +0000, Lofstedt, Marta wrote:
> >> The issue is describe more in detail here:
> >> https://bugs.freedesktop.org/show_bug.cgi?id=100548
> >
> > I don't click links.
>
> Frankly, I find that more than a little offensive response to a
> regression report.
*shrug*, its more than you would've gotten if you'd filed a kernel
bugzilla. Those go straight to /dev/null.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-04-12 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 12:04 freedesktop bug id: 100548, bisected to sched/clock commit Lofstedt, Marta
2017-04-12 12:31 ` Peter Zijlstra
2017-04-12 13:30 ` Jani Nikula
2017-04-12 14:28 ` Peter Zijlstra [this message]
2017-04-12 13:40 ` Martin Peres
2017-04-12 14:32 ` Peter Zijlstra
2017-04-12 14:49 ` Martin Peres
2017-04-12 15:50 ` Peter Zijlstra
2017-04-13 11:48 ` Peter Zijlstra
2017-04-13 12:30 ` Martin Peres
2017-04-13 13:23 ` Peter Zijlstra
2017-04-13 14:55 ` Thomas Gleixner
2017-04-18 14:10 ` Lofstedt, Marta
2017-04-18 15:53 ` Peter Zijlstra
2017-04-20 17:19 ` Peter Zijlstra
2017-04-20 19:36 ` Peter Zijlstra
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=20170412142809.awtdkxr4fguivjkz@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=martin.peres@intel.com \
--cc=pasha.tatashin@oracle.com \
/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.