linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
	Andreas Sturmlechner <andreas.sturmlechner@gmail.com>,
	stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: 3.4.10 i915 [GM45] regression
Date: Thu, 27 Sep 2012 13:25:53 -0700	[thread overview]
Message-ID: <20120927202553.GA19276@kroah.com> (raw)
In-Reply-To: <20120927185917.GC3211@herton-Z68MA-D2H-B3>

On Thu, Sep 27, 2012 at 03:59:18PM -0300, Herton Ronaldo Krzesinski wrote:
> On Wed, Sep 26, 2012 at 04:42:23PM -0700, Greg KH wrote:
> > On Mon, Sep 10, 2012 at 11:07:38AM -0300, Herton Ronaldo Krzesinski wrote:
> > > On Mon, Sep 10, 2012 at 10:58:03AM -0300, Herton Ronaldo Krzesinski wrote:
> > > > Couldn't it be that it happens because 3.4 doesn't have commits
> > > > b7884eb45ec98c0d34c7f49005ae9d4b4b4e38f6 and
> > > > f01db988ef6f6c70a6cc36ee71e4a98a68901229 applied? May be they are needed
> > > > after all.
> > > 
> > > Nevermind, the description on the freedesktop bug report states that
> > > these commits were already tried and didn't work (if "3.4.10 + follow-up
> > > patches in Herton's reply - failed" means it)
> > 
> > Did anything ever come from this?  I haven't reverted anything, or
> > applied anything different, so if something needs to be done here,
> > please let me know.
> 
> I think the conclusion looking at the bug report
> (https://bugs.freedesktop.org/show_bug.cgi?id=54575) is
> that the commit 0d8957c8a90bbb5d34fab9a304459448a5131e06 should be 
> reverted on 3.4, please correct me if I'm wrong.

Daniel, do you agree with this?

thanks,

greg k-h

  reply	other threads:[~2012-09-27 20:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07  0:27 3.4.10 i915 [GM45] regression Andreas Sturmlechner
2012-09-07  1:15 ` Greg KH
2012-09-07  1:57   ` Andreas Sturmlechner
2012-09-07  9:37     ` Daniel Vetter
2012-09-10 13:58       ` Herton Ronaldo Krzesinski
2012-09-10 14:07         ` Herton Ronaldo Krzesinski
2012-09-26 23:42           ` Greg KH
2012-09-27 18:59             ` Herton Ronaldo Krzesinski
2012-09-27 20:25               ` Greg KH [this message]
2012-09-28  6:16                 ` Daniel Vetter
2012-09-28 16:06                   ` Greg KH
2012-09-30 11:15                     ` Andreas Sturmlechner
2012-09-30 14:32                       ` Greg KH
2012-10-01  7:24                         ` Daniel Vetter
2012-10-01 21:56                           ` Andreas Sturmlechner
2012-10-02  7:17                             ` Daniel Vetter
2012-10-04 22:28                               ` Greg KH
2012-10-05 19:27                               ` Andreas Sturmlechner
2012-10-07 13:46                   ` Ben Hutchings
2012-09-27 20:48             ` Andreas Sturmlechner
2012-09-27 21:12               ` Andreas Sturmlechner

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=20120927202553.GA19276@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.sturmlechner@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=herton.krzesinski@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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 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).