From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-can@vger.kernel.org
Subject: Re: [can:for-davem 18/19] net/can/gw.c:370:13: sparse: restricted __wsum degrades to integer
Date: Wed, 23 Jan 2013 10:18:54 +0100 [thread overview]
Message-ID: <50FFAAFE.7030405@pengutronix.de> (raw)
In-Reply-To: <50FFA819.8060708@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On 01/23/2013 10:06 AM, Oliver Hartkopp wrote:
> Hello Marc,
>
> it was hard to make sparse to give this warning on my machine ...
>
> For the records:
>
> make C=1 CF="-D__CHECK_ENDIAN__"
>
> made it :-)
>
>
> I pushed a new commit to the cangw branch of ollis-can-next:
>
> https://gitorious.org/~hartkopp/linux-can/ollis-can-next/commits/cangw
>
> The commit is
>
> https://gitorious.org/~hartkopp/linux-can/ollis-can-next/commit/4068160ad6f42436a40edf4b04ec47e86399b544
I've squashed the commit into "can: gw: add a variable limit for CAN
frame routings" and pushed the resulting tree to linux-can-next/for-davem
tnx,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-01-23 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 1:26 [can:for-davem 18/19] net/can/gw.c:370:13: sparse: restricted __wsum degrades to integer kbuild test robot
2013-01-23 9:06 ` Oliver Hartkopp
2013-01-23 9:18 ` Marc Kleine-Budde [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=50FFAAFE.7030405@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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.