mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kevin Winchester <kjwinchester@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>,
	Dave Airlie <airlied@linux.ie>,
	dri-devel <dri-devel@lists.sf.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Alex Deucher <alexdeucher@gmail.com>,
	Jerome Glisse <jglisse@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	John Kacur <jkacur@gmail.com>
Subject: Re: Radeon KMS regression still present in 2.6.33-rc6
Date: Sat, 30 Jan 2010 20:29:41 -0400	[thread overview]
Message-ID: <1264897781.1528.7.camel@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.1001301153390.4206@localhost.localdomain>

On Sat, 2010-01-30 at 11:54 -0800, Linus Torvalds wrote:
> 
> On Sat, 30 Jan 2010, Johannes Hirte wrote:
> > 
> > This is caused by commit 42590a75019a50012f25a962246498dead42843
> > 
> > Fix is already posted:
> > 
> > http://marc.info/?l=linux-kernel&m=126428141429200&w=2
> 
> Goodie. Kevin, can you test the patch from FUJITA Tomonori in that thread 
> ("http://marc.info/?l=linux-kernel&m=126439631307219&w=2" to be exact).
> 

Thank you - the patch from FUJITA Tomonori corrected the issue.

I also tried out the additional patches from John Kacur.  They did not
break anything that I could see, and the logic behind them seems
reasonable to me.  They weren't necessary to fix my problem though, so I
guess they are likely not 2.6.33 material (unless they are critical for
someone else).

Thanks again to everyone who looked into the problem,

-- 
Kevin Winchester




  parent reply	other threads:[~2010-01-31  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30 17:18 Kevin Winchester
2010-01-30 17:43 ` Linus Torvalds
2010-01-30 19:50   ` Johannes Hirte
2010-01-30 19:54     ` Linus Torvalds
2010-01-30 20:49       ` John Kacur
2010-01-31  0:29       ` Kevin Winchester [this message]
2010-02-01 18:56         ` Linus Torvalds

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=1264897781.1528.7.camel@localhost.localdomain \
    --to=kjwinchester@gmail.com \
    --cc=airlied@linux.ie \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.sf.net \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=jglisse@redhat.com \
    --cc=jkacur@gmail.com \
    --cc=johannes.hirte@fem.tu-ilmenau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®