public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse•com>
To: Guenter Roeck <linux@roeck-us•net>
Cc: Paul Gortmaker <paul.gortmaker@windriver•com>,
	"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
	Ingo Molnar <mingo@kernel•org>
Subject: Re: Build error in -next due to 'drivers/video/fbdev/atyfb: Replace MTRR UC hole with strong UC'
Date: Sat, 1 Aug 2015 02:39:33 +0200	[thread overview]
Message-ID: <20150801003933.GT30479@wotan.suse.de> (raw)
In-Reply-To: <55BC0E50.9060606@roeck-us.net>

On Fri, Jul 31, 2015 at 05:09:52PM -0700, Guenter Roeck wrote:
> On 07/31/2015 05:02 PM, Luis R. Rodriguez wrote:
> >On Fri, Jul 31, 2015 at 01:52:24PM -0400, Paul Gortmaker wrote:
> >>On Thu, Jul 30, 2015 at 10:26 PM, Guenter Roeck <linux@roeck-us•net> wrote:
> >>>Hi Luis,
> >>>
> >>>probably the zero-day build already told you, but just in case:
> >>>
> >>>Your commit 'drivers/video/fbdev/atyfb: Replace MTRR UC hole with strong UC'
> >>>causes build errors for architectures which don't support ioremap_uc.
> >>>This affects at least the alpha architecture, though there may be others.
> >>
> >>Yep, parisc allmodconfig now sees it as well.  Bisected before seeing
> >>this message.
> >>
> >>3cc2dac5be3f23414a4efdee0b26d79bed297cac is the first bad commit
> >>commit 3cc2dac5be3f23414a4efdee0b26d79bed297cac
> >>Author: Luis R. Rodriguez <mcgrof@suse•com>
> >>Date:   Thu Jul 9 18:24:58 2015 -0700
> >>
> >>     drivers/video/fbdev/atyfb: Replace MTRR UC hole with strong UC
> >>
> >>http://kisskb.ellerman.id.au/kisskb/buildresult/12475234/
> >
> >I submitted a fix for it, can you tell me your linux-next tree?
> >
> 
> http://server.roeck-us.net:8010/builders/next-alpha-next
> 
> next-20150729 to next-20150731.

Great thanks, I sent a proposal general fix, that should be tested first.
If all the bots say go for it, then yay, otherwise a simple

#define ioremap_uc ioremap_nocache

would be the way to go, but I would prefer to fix this sort of thing for good.

  Luis

  reply	other threads:[~2015-08-01  0:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  2:26 Build error in -next due to 'drivers/video/fbdev/atyfb: Replace MTRR UC hole with strong UC' Guenter Roeck
2015-07-31 17:52 ` Paul Gortmaker
2015-08-01  0:02   ` Luis R. Rodriguez
2015-08-01  0:09     ` Guenter Roeck
2015-08-01  0:39       ` Luis R. Rodriguez [this message]
2015-08-01  1:05         ` Guenter Roeck

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=20150801003933.GT30479@wotan.suse.de \
    --to=mcgrof@suse$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux@roeck-us$(echo .)net \
    --cc=mingo@kernel$(echo .)org \
    --cc=paul.gortmaker@windriver$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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