mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@suse.de>
Subject: Re: drivers/video/fbdev/aty/atyfb_base.c:3461:2: error: implicit declaration of function 'ioremap_uc'
Date: Mon, 7 Mar 2016 21:29:37 +0100	[thread overview]
Message-ID: <20160307202937.GB22229@wotan.suse.de> (raw)
In-Reply-To: <201603062005.lhOBibd1%fengguang.wu@intel.com>


I'll send a fix. I  have it written.

 Luis

On Sun, Mar 06, 2016 at 08:14:07PM +0800, kbuild test robot wrote:
> Hi Luis,
> 
> FYI, the error/warning still remains.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   67944024c1cdd897e49a09b0d6af3ea38d1388ca
> commit: 3cc2dac5be3f23414a4efdee0b26d79bed297cac drivers/video/fbdev/atyfb: Replace MTRR UC hole with strong UC
> date:   8 months ago
> config: ia64-allyesconfig (attached as .config)
> reproduce:
>         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         git checkout 3cc2dac5be3f23414a4efdee0b26d79bed297cac
>         # save the attached .config to linux build tree
>         make.cross ARCH=ia64 
> 
> All errors (new ones prefixed by >>):
> 
>    drivers/video/fbdev/aty/atyfb_base.c: In function 'atyfb_setup_generic':
> >> drivers/video/fbdev/aty/atyfb_base.c:3461:2: error: implicit declaration of function 'ioremap_uc' [-Werror=implicit-function-declaration]
>      par->ati_regbase = ioremap_uc(info->fix.mmio_start, 0x1000);
>      ^
>    drivers/video/fbdev/aty/atyfb_base.c:3461:19: warning: assignment makes pointer from integer without a cast
>      par->ati_regbase = ioremap_uc(info->fix.mmio_start, 0x1000);
>                       ^
>    cc1: some warnings being treated as errors
> 
> vim +/ioremap_uc +3461 drivers/video/fbdev/aty/atyfb_base.c
> 
>   3455	
>   3456		info->fix.mmio_start = raddr;
>   3457		/*
>   3458		 * By using strong UC we force the MTRR to never have an
>   3459		 * effect on the MMIO region on both non-PAT and PAT systems.
>   3460		 */
> > 3461		par->ati_regbase = ioremap_uc(info->fix.mmio_start, 0x1000);
>   3462		if (par->ati_regbase == NULL)
>   3463			return -ENOMEM;
>   3464	
> 
> ---
> 0-DAY kernel test infrastructure                Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all                   Intel Corporation



-- 
Luis Rodriguez, SUSE LINUX GmbH
Maxfeldstrasse 5; D-90409 Nuernberg

  reply	other threads:[~2016-03-07 20:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06 12:14 kbuild test robot
2016-03-07 20:29 ` Luis R. Rodriguez [this message]
2016-03-07 20:34 ` [PATCH] ia64: define ioremap_uc() Luis R. Rodriguez
2016-03-15 22:07   ` Luis R. Rodriguez
2016-03-15 22:15     ` Luck, Tony
2016-03-15 22:13   ` Andrew Morton
2016-03-15 22:17     ` Luck, Tony
  -- strict thread matches above, loose matches on Subject: below --
2016-02-28 11:18 drivers/video/fbdev/aty/atyfb_base.c:3461:2: error: implicit declaration of function 'ioremap_uc' kbuild test robot

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=20160307202937.GB22229@wotan.suse.de \
    --to=mcgrof@suse.com \
    --cc=bp@suse.de \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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

all inboxes | Powered by JetHome®