linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sylvester.nawrocki@gmail.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch] [media] exynos4-is: cleanup a define
Date: Fri, 08 Nov 2013 23:17:32 +0100	[thread overview]
Message-ID: <527D62FC.3010001@gmail.com> (raw)
In-Reply-To: <20131108095224.GJ27977@elgon.mountain>


(dropping some unrelated e-mail addresses from Cc)

On 11/08/2013 10:52 AM, Dan Carpenter wrote:
> This define is only used in s5pcsis_irq_handler():
>
> 	if ((status&  S5PCSIS_INTSRC_NON_IMAGE_DATA)&&  pktbuf->data) {
>
> The problem is that "status" is a 32 bit and (0xff<<  28) is larger than
> 32 bits and that sets off a static checker warning.  I consulted with
> Sylwester Nawrocki and the define should actually be (0xf<<  28).
>
> Signed-off-by: Dan Carpenter<dan.carpenter@oracle.com>

Thanks for the fix, patch added to my tree for v3.14.

> diff --git a/drivers/media/platform/exynos4-is/mipi-csis.c b/drivers/media/platform/exynos4-is/mipi-csis.c
> index 9fc2af6..31dfc50 100644
> --- a/drivers/media/platform/exynos4-is/mipi-csis.c
> +++ b/drivers/media/platform/exynos4-is/mipi-csis.c
> @@ -91,7 +91,7 @@ MODULE_PARM_DESC(debug, "Debug level (0-2)");
>   #define S5PCSIS_INTSRC_ODD_BEFORE	(1<<  29)
>   #define S5PCSIS_INTSRC_ODD_AFTER	(1<<  28)
>   #define S5PCSIS_INTSRC_ODD		(0x3<<  28)
> -#define S5PCSIS_INTSRC_NON_IMAGE_DATA	(0xff<<  28)
> +#define S5PCSIS_INTSRC_NON_IMAGE_DATA	(0xf<<  28)
>   #define S5PCSIS_INTSRC_FRAME_START	(1<<  27)
>   #define S5PCSIS_INTSRC_FRAME_END	(1<<  26)
>   #define S5PCSIS_INTSRC_ERR_SOT_HS	(0xf<<  12)

--
Regards,
Sylwester

      reply	other threads:[~2013-11-08 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  9:52 [patch] [media] exynos4-is: cleanup a define Dan Carpenter
2013-11-08 22:17 ` Sylwester Nawrocki [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=527D62FC.3010001@gmail.com \
    --to=sylvester.nawrocki@gmail.com \
    --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).