linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/9] ARM i.MX5: Add IPU device support
Date: Thu, 28 Apr 2011 17:51:00 +0100	[thread overview]
Message-ID: <20110428165059.GY17290@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1303738709-27562-1-git-send-email-weitway@gmail.com>

On Mon, Apr 25, 2011 at 09:38:29PM +0800, weitway at gmail.com wrote:
> +#include <mach/ipu-v3.h>
> +struct imx_ipuv3_data {
> +	resource_size_t iobase;
> +	resource_size_t iosize;
> +	resource_size_t irq_err;
> +	resource_size_t irq;

IRQs don't need to be resource_size_t.  They're treated as 'int's by
the request_irq() API, so high bits get truncated anyway.  Keep them
as int or unsigned int in this structure and just allow the compiler
to promote them as required to resource_size_t on assignment.

      reply	other threads:[~2011-04-28 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25 13:38 [PATCH 2/9] ARM i.MX5: Add IPU device support weitway at gmail.com
2011-04-28 16:51 ` Russell King - ARM Linux [this message]

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=20110428165059.GY17290@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).