From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "w@1wt.eu" <w@1wt.eu>, "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: i915 drm patches in LTS 4.4.x ?
Date: Tue, 19 Jul 2016 15:08:16 -0700 [thread overview]
Message-ID: <20160719220816.GB1948@kroah.com> (raw)
In-Reply-To: <1468946661.3487.47.camel@infinera.com>
On Tue, Jul 19, 2016 at 04:43:06PM +0000, Joakim Tjernlund wrote:
> On Tue, 2016-07-19 at 10:59 +0200, Willy Tarreau wrote:
> > On Tue, Jul 19, 2016 at 08:41:21AM +0000, Joakim Tjernlund wrote:
> > >
> > > >
> > > > Did you try it or at least the kernel which contains it ? It is important
> > >
> > > No I haven't. I myself do not have such a laptop so I must find someone that does
> > > and willing to test stuff for me(I maintain our Linux DE used for in-house development)
> > > All I can say for sure is that 4.1.x works and 4.4.x does not :(
> >
> > OK that's already a good indication.
> >
> > (...)
> > >
> > > Yes I get that but I figured that a upstream commit that is marked:
> > > �Cc: <stable@vger.kernel.org> # v4.2+
> > > already was approved for stable and it would find its way into all relevant branches.
> >
> > Indeed it could be one candidate, so if you can afford to wait for a
> > next release to see if it fixes your problem that's the easiest way.
> > Otherwise you'll have to bisect either between 4.1 and 4.4 to find
> > which one broke, or to test mainline to see if it's fixed again. But
> > given that it was a regression, it's likely that someone else will
> > notice it and propose a fix (possibly the one above).
> >�
>
> Yes, plenty of people have similar has a problem but Intel devs have had hard time
> finding the bugs.
>
> Greg, could push your mail queue so I can compare with upstream?
I don't know what you mean by that, I'm not going to push my stable mbox
up publicly, sorry :)
> Seems like this patch has been lost though:
> �[PATCH stable-4.4] drm/i915: Update CDCLK_FREQ register on BDW after changing cdclk frequency
Not lost, still in my todo queue, along with 663 other patches I need to
review/apply...
thanks,
greg k-h
next prev parent reply other threads:[~2016-07-19 22:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:21 i915 drm patches in LTS 4.4.x ? Joakim Tjernlund
2016-07-18 20:52 ` Greg KH
2016-07-18 23:41 ` Joakim Tjernlund
2016-07-19 5:26 ` Willy Tarreau
2016-07-19 8:41 ` Joakim Tjernlund
2016-07-19 8:59 ` Willy Tarreau
2016-07-19 16:43 ` Joakim Tjernlund
2016-07-19 22:08 ` gregkh [this message]
2016-07-20 8:49 ` Joakim Tjernlund
2016-07-20 8:58 ` Willy Tarreau
2016-07-20 10:48 ` Joakim Tjernlund
2016-07-24 23:43 ` gregkh
2016-07-19 22:06 ` gregkh
2016-07-20 8:41 ` Joakim Tjernlund
2016-07-24 23:41 ` gregkh
2016-07-25 11:39 ` Joakim Tjernlund
2016-07-25 12:01 ` Joakim Tjernlund
2016-07-25 20:26 ` gregkh
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=20160719220816.GB1948@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Joakim.Tjernlund@infinera.com \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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.