From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: More build errors and warnings
Date: Mon, 20 Feb 2012 09:55:32 -0800 [thread overview]
Message-ID: <20120220175532.GL18185@atomide.com> (raw)
In-Reply-To: <20120220075322.GA22675@n2100.arm.linux.org.uk>
Hi Russell & Ohad,
* Russell King - ARM Linux <linux@arm.linux.org.uk> [120219 23:22]:
> Errors:
>
> arch/arm/mach-omap2/built-in.o: In function `n8x0_mmc_callback': twl-common.c:(.text+0x108a0): undefined reference to `omap_mmc_notify_cover_event'</pre><h2>Warnings
I'll post a fix to do a warning here if the cover events
are unavailable. The long term fix is to let the MMC driver
register the callback with the PMIC to do this.
> Warnings:
>
> drivers/iommu/omap-iommu-debug.c:271: warning: passing argument 1 of 'omap_find_iovm_area' from incompatible pointer type
> drivers/iommu/omap-iommu-debug.c:308: warning: passing argument 1 of 'omap_find_iovm_area' from incompatible pointer type
>
> These two are a serious problem, which needs fixing for -rc:
>
> omap-iommu-debug.c:
> struct omap_iommu *obj = file->private_data;
>
> area = omap_find_iovm_area(obj, (u32)ppos);
>
> arch/arm/plat-omap/include/plat/iovmm.h:extern struct iovm_struct *omap_find_iovm_area(struct device *dev, u32 da);
>
> Config file (for the next 7 days):
> http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=170
Ohad, care to look into fixing these for the -rc series?
Regards,
Tony
next prev parent reply other threads:[~2012-02-20 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 7:53 More build errors and warnings Russell King - ARM Linux
2012-02-20 17:55 ` Tony Lindgren [this message]
2012-02-20 18:01 ` Ohad Ben-Cohen
2012-02-20 18:06 ` [PATCH] ARM: OMAP: Fix build error when mmc_omap is built as module Tony Lindgren
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=20120220175532.GL18185@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ohad@wizery.com \
/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.