All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Andre Heider <a.heider@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [pull] radeon drm-fixes-3.11
Date: Wed, 17 Jul 2013 16:26:19 -0400	[thread overview]
Message-ID: <CADnq5_OJbiR+3cevJ3yuiV9MuWOP+mB6qbqOCoABR82r4dAtHQ@mail.gmail.com> (raw)
In-Reply-To: <CAHsu+b_6nQENKc5Z3+fH=2MW1Bnm0G5mdGR7HP1YqqOi_Bzs4g@mail.gmail.com>

Dave hold off on this for now.

Alex


On Wed, Jul 17, 2013 at 4:24 PM, Andre Heider <a.heider@gmail.com> wrote:
> On Wed, Jul 17, 2013 at 9:54 PM,  <alexdeucher@gmail.com> wrote:
>> From: Alex Deucher <alexander.deucher@amd.com>
>>
>> Hi Dave,
>>
>> Just a few DPM fixes.
>>
>> The following changes since commit d1ce3d5496f2a7c90dd00a9133572f931d2acdcc:
>>
>>   uvesafb: Really allow mtrr being 0, as documented and warn()ed (2013-07-16 10:24:28 +1000)
>>
>> are available in the git repository at:
>>   git://people.freedesktop.org/~agd5f/linux drm-fixes-3.11
>>
>> Alex Deucher (3):
>>       drm/radeon: add a module parameter to disable aspm
>>       drm/radeon: fix an endian bug in atom table parsing
>>       drm/radeon/dpm: fix atom vram table parsing
>>
>> Andre Heider (1):
>>       drm/radeon/dpm/atom: restructure logic to work around a compiler bug
>
> Discarding the debug patches from bug #66932 and then merging your
> branch makes it break again :P
> Seems like the printk()s mattered and the gcc 4.8 still hates the code.
>
> I still think its due to the asRegIndexBuf[1] definition + accessing
> the array with i>0, let me poke at it a little

  reply	other threads:[~2013-07-17 20:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 19:54 [pull] radeon drm-fixes-3.11 alexdeucher
2013-07-17 20:24 ` Andre Heider
2013-07-17 20:26   ` Alex Deucher [this message]
2013-07-17 20:36   ` Alex Deucher
2013-07-17 21:05 ` alexdeucher
  -- strict thread matches above, loose matches on Subject: below --
2013-08-15 17:06 Alex Deucher
2013-08-14 22:11 Alex Deucher
2013-08-07 22:15 Alex Deucher
2013-08-08  4:37 ` Rafał Miłecki
2013-08-08 12:18   ` Deucher, Alexander
2013-07-29 22:39 alexdeucher
2013-07-30 21:38 ` alexdeucher
2013-07-23 12:37 alexdeucher
2013-07-26  2:05 ` alexdeucher
2013-07-15 20:42 alexdeucher

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=CADnq5_OJbiR+3cevJ3yuiV9MuWOP+mB6qbqOCoABR82r4dAtHQ@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=a.heider@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.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.