From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
linux-omap@vger.kernel.org, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 07/07] ARM: OMAP2: Fix sparse, checkpatch warnings in OMAP2/3 IRQ code
Date: Thu, 9 Oct 2008 15:37:55 +0100 [thread overview]
Message-ID: <20081009143755.GF435@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1223035009-23866-8-git-send-email-tony@atomide.com>
On Fri, Oct 03, 2008 at 02:56:49PM +0300, Tony Lindgren wrote:
> Fix sparse warnings in mach-omap2/irq.c. Fix by defining
> intc_bank_write_reg() and intc_bank_read_reg(), and convert INTC module
> register access to use them rather than __raw_{read,write}l.
This is not a fix.
> +/* INTC bank register get/set */
> +
> +static void intc_bank_write_reg(u32 val, struct omap_irq_bank *bank, u16 reg)
> +{
> + __raw_writel(val, (__force void __iomem *)(bank->base_reg + reg));
> +}
> +
> +static u32 intc_bank_read_reg(struct omap_irq_bank *bank, u16 reg)
> +{
> + return __raw_readl((__force void __iomem *)(bank->base_reg + reg));
Because it uses __force here. In my tree, bank->base_reg is defined
to be:
void __iomem *base_reg;
So these cases are entirely unnecessary. As I've said before, use of
__force is generally a sure sign of doing something wrong.
next prev parent reply other threads:[~2008-10-09 14:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 11:56 [PATCH 0/0] Refreshed omap2 patches, v3 Tony Lindgren
2008-10-03 11:56 ` [PATCH 01/07] ARM: OMAP2 Provide function to enable/disable uart clocks Tony Lindgren
2008-10-03 11:56 ` [PATCH 02/07] ARM: OMAP2: Move sleep.S into sleep24xx.S Tony Lindgren
2008-10-03 11:56 ` [PATCH 03/07] ARM: OMAP2: Use omap_globals for CPU detection for multi-omap Tony Lindgren
2008-10-03 11:56 ` [PATCH 04/07] ARM: OMAP2: Add pinmux support for omap34xx Tony Lindgren
2008-10-03 11:56 ` [PATCH 05/07] ARM: OMAP2: Fix sparse, checkpatch warnings fro GPMC code, use ioremap Tony Lindgren
2008-10-03 11:56 ` [PATCH 06/07] ARM: OMAP2: Misc updates from linux-omap tree Tony Lindgren
2008-10-03 11:56 ` [PATCH 07/07] ARM: OMAP2: Fix sparse, checkpatch warnings in OMAP2/3 IRQ code Tony Lindgren
2008-10-09 14:37 ` Russell King - ARM Linux [this message]
2008-10-09 15:04 ` Tony Lindgren
2008-10-08 7:39 ` [PATCH 06/07] ARM: OMAP2: Misc updates from linux-omap tree, v3 Tony Lindgren
2008-10-09 15:02 ` [PATCH 06/07] ARM: OMAP2: Misc updates from linux-omap tree, v4 Tony Lindgren
2008-10-03 12:13 ` [PATCH 0/0] Refreshed omap2 patches, v3 Tony Lindgren
2008-10-08 7:42 ` git-pull request for omap2 changes (Re: [PATCH 0/0] Refreshed omap2 patches, v3) 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=20081009143755.GF435@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=tony@atomide.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.