From: Marek Vasut <marex@denx.de>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
"Marc Kleine-Budde" <mkl@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Mark Rutland <mark.rutland@arm.com>,
Wolfgang Grandegger <wg@grandegger.com>
Subject: Re: [PATCH 5/5] net: can: ifi: Add IFI CANFD IP support
Date: Mon, 11 Jan 2016 20:33:11 +0100 [thread overview]
Message-ID: <201601112033.11487.marex@denx.de> (raw)
In-Reply-To: <201601120324.lYD7L0Bs%fengguang.wu@intel.com>
On Monday, January 11, 2016 at 08:29:28 PM, kbuild test robot wrote:
> Hi Marek,
Hi Robot,
> [auto build test WARNING on net/master]
> [also build test WARNING on v4.4 next-20160111]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improving the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Marek-Vasut/net-can-Sort-the-Kcon
> fig-includes/20160112-025020 config: x86_64-allmodconfig (attached as
> .config)
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All warnings (new ones prefixed by >>):
>
> drivers/net/can/ifi_canfd/ifi_canfd.c: In function 'ifi_canfd_isr':
> >> drivers/net/can/ifi_canfd/ifi_canfd.c:486:27: warning: large integer
> >> implicitly truncated to unsigned type [-Woverflow]
>
> const u32 clr_irq_mask = ~(IFI_CANFD_INTERRUPT_SET_IRQ |
> ^
> drivers/net/can/ifi_canfd/ifi_canfd.c: In function 'ifi_canfd_start':
> drivers/net/can/ifi_canfd/ifi_canfd.c:640:9: warning: large integer
> implicitly truncated to unsigned type [-Woverflow]
> writel(~IFI_CANFD_INTERRUPT_SET_IRQ, priv->base + IFI_CANFD_INTERRUPT); ^
> drivers/net/can/ifi_canfd/ifi_canfd.c: In function 'ifi_canfd_stop':
> drivers/net/can/ifi_canfd/ifi_canfd.c:675:9: warning: large integer
> implicitly truncated to unsigned type [-Woverflow]
> writel(~IFI_CANFD_INTERRUPT_SET_IRQ, priv->base + IFI_CANFD_INTERRUPT); ^
How did this splat came to be ? I would expect that the expansion goes like
this:
const u32 clr_irq_mask = ~(IFI_CANFD_INTERRUPT_SET_IRQ |
IFI_CANFD_INTERRUPT_ERROR_WARNING);
const u32 clr_irq_mask = ~(BIT(31) | BIT(1));
const u32 clr_irq_mask = ~(0x80000002);
const u32 clr_irq_mask = 0x7ffffffd;
Did I miss something there ?
Thanks!
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-01-11 19:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 18:47 [PATCH 1/5] net: can: Sort the Kconfig includes Marek Vasut
2016-01-11 18:48 ` [PATCH 2/5] net: can: Sort the Makefile Marek Vasut
2016-01-11 18:48 ` [PATCH 3/5] of: Add vendor prefix for I/F/I Marek Vasut
2016-01-11 18:48 ` [PATCH 4/5] net: can: ifi: Add DT bindings for ifi,canfd Marek Vasut
2016-01-11 18:48 ` [PATCH 5/5] net: can: ifi: Add IFI CANFD IP support Marek Vasut
2016-01-11 19:29 ` kbuild test robot
2016-01-11 19:33 ` Marek Vasut [this message]
2016-01-12 11:06 ` kbuild test robot
2016-01-12 23:59 ` [PATCH V2 " Marek Vasut
2016-01-20 10:39 ` Marc Kleine-Budde
2016-01-20 10:54 ` Marc Kleine-Budde
2016-01-20 12:58 ` Marek Vasut
2016-01-20 14:06 ` Marc Kleine-Budde
2016-01-20 14:25 ` Marek Vasut
2016-01-23 0:11 ` Rustad, Mark D
2016-01-20 14:33 ` [PATCH V3 " Marek Vasut
2016-01-20 14:39 ` Marc Kleine-Budde
2016-01-20 14:41 ` Marek Vasut
2016-01-20 14:46 ` Marc Kleine-Budde
2016-01-20 15:03 ` Marek Vasut
2016-01-20 15:09 ` Marc Kleine-Budde
2016-01-20 15:40 ` Marek Vasut
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=201601112033.11487.marex@denx.de \
--to=marex@denx.de \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.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 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).