From: Jani Nikula <jani.nikula@linux.intel.com>
To: Martin Kepplinger <martink@posteo.de>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Joerg Roedel <jroedel@suse.de>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
torvalds@linux-foundation.org, daniel.vetter@intel.com
Subject: Re: [BUG][REGRESSION] mangled display since -rc1
Date: Mon, 07 Nov 2016 10:24:34 +0200 [thread overview]
Message-ID: <87zilb8zp9.fsf@intel.com> (raw)
In-Reply-To: <0f63c442-29c0-bcf7-2f0b-a2733eb7794b@posteo.de>
On Sun, 06 Nov 2016, Martin Kepplinger <martink@posteo.de> wrote:
> I did not file a bug in bugzilla yet. I haven't given up that we can fix
> this here before the release. I've ignored it the last few days though.
You say it like filing the bug report and having the bug fixed are
mutually exclusive things...
Pretty please? It's easier for us to direct folks at the bug, with
history and logs in one place. I realize only Daniel and me were Cc'd
here, not intel-gfx list.
Also, please double check your bisect. Not sure why the finger points at
i915 when the bisect points at iommu merge.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2016-11-07 8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 10:36 [BUG][REGRESSION] mangled display since -rc1 Martin Kepplinger
2016-10-31 10:40 ` Martin Kepplinger
2016-10-31 15:21 ` Joerg Roedel
2016-10-31 20:44 ` Martin Kepplinger
2016-10-31 21:54 ` Joerg Roedel
2016-11-01 11:27 ` Martin Kepplinger
2016-11-01 11:47 ` Jani Nikula
2016-11-06 11:21 ` Thorsten Leemhuis
2016-11-06 11:43 ` Martin Kepplinger
2016-11-06 13:02 ` Martin Kepplinger
2016-11-07 8:24 ` Jani Nikula [this message]
2016-11-07 15:34 ` Martin Kepplinger
2016-11-07 16:01 ` Martin Steigerwald
2016-11-07 16:07 ` Martin Kepplinger
2016-11-07 17:36 ` Jani Nikula
2016-11-13 21:32 ` Martin Kepplinger
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=87zilb8zp9.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
--cc=regressions@leemhuis.info \
--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 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.