From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tuncer Ayaz <tuncer.ayaz@gmail.com>
Cc: alexander.levin@verizon.com,
"daniel.vetter\@intel.com" <daniel.vetter@intel.com>,
"seanpaul\@chromium.org" <seanpaul@chromium.org>,
"airlied\@linux.ie" <airlied@linux.ie>,
"dri-devel\@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable\@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: 4.1 EOL
Date: Thu, 16 Nov 2017 11:13:05 +0200 [thread overview]
Message-ID: <8760aa7fj2.fsf@intel.com> (raw)
In-Reply-To: <CAOvwQ4jPKjCXWfDuAX7vzvm=sBjBhWS8hkrQy4ENXgcpO7cbnQ@mail.gmail.com>
On Wed, 15 Nov 2017, Tuncer Ayaz <tuncer.ayaz@gmail.com> wrote:
> I don't follow why you think it's a different platform and how I might
> have "more" definitely shown v4.1 to be good, but I'll trust your
> judgement as a drm dev and not argue :).
You apparently have Sandy Bridge, the referenced reports are about
Broadwell and Skylake. Even if the symptoms you see are the same, the
root causes might be wildly different, needing a different fix.
I've learned the hard way not to make assumptions without detailed
information, which in this case I don't have. As in, I don't even know
for sure if you have Sandy Bridge or not, although it's alluded to in
your message.
>From my point of view, you're shouting regression while giving us
nothing to work with. You need to help us to help you.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-11-16 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOvwQ4i_VTLg_P-mCTesTvUENYmtix1MfbmFQ=WTC6UUT-DroA@mail.gmail.com>
[not found] ` <20171111200025.hz6zbcqy7uacqd2s@sasha-lappy>
[not found] ` <CAOvwQ4hsy1CSKGCwm_Y+j-VGpmXMAF_vhg+WnifphhxVd3ur8A@mail.gmail.com>
2017-11-13 21:00 ` 4.1 EOL alexander.levin
2017-11-14 8:46 ` Jani Nikula
2017-11-14 21:41 ` Tuncer Ayaz
2017-11-15 10:04 ` Jani Nikula
2017-11-15 17:00 ` Tuncer Ayaz
2017-11-16 9:13 ` Jani Nikula [this message]
2017-11-17 7:42 ` Tuncer Ayaz
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=8760aa7fj2.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=alexander.levin@verizon.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=stable@vger.kernel.org \
--cc=tuncer.ayaz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).