From: Patrick Menschel <menschel.p@posteo.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>, Michael Luxen <mluxen@gmx.net>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: can-isotp-modules
Date: Wed, 30 Mar 2016 15:24:10 +0200 [thread overview]
Message-ID: <56FBD37A.2080600@posteo.de> (raw)
In-Reply-To: <56FBC475.1070703@hartkopp.net>
[-- Attachment #1: Type: text/plain, Size: 1977 bytes --]
Am 30.03.2016 um 14:20 schrieb Oliver Hartkopp:
>
>
> On 03/28/2016 11:43 AM, Patrick Menschel wrote:
>> Hello Michael,
>>
>> I'd like to ask if there are other preconditions about compiling isotp
>> on the bbb.
>>
>> I recently purchased a bbb and I'm currently trying to compile modules
>> for
>>
>> 4.1.15-ti-rt-r43
>
> '-rt-' looks like 'real time'
>
> Can you send the output of the warnings and errors?
About 25000 lines with multiple occurrences of macro and null character
errors of this kind.
include/linux/export.h:1:1: warning: null character(s) ignored
include/linux/byteorder/generic.h:96:21: note: in expansion of macro
‘__be16_to_cpu’
#define be16_to_cpu __be16_to_cpu
looks almost the same as what Michael posted on 03.11.2015 23:29
> root@beaglebone:~/can-isotp-modules# make
> make -C /lib/modules/4.1.6-ti-r16/build M=/root/can-isotp-modules modules TOPDIR=/root/can-isotp-modules
> make[1]: Entering directory '/usr/src/linux-headers-4.1.6-ti-r16'
> CC [M] /root/can-isotp-modules/drivers/net/can/vcan.o
> In file included from include/linux/module.h:17:0,
> from /root/can-isotp-modules/drivers/net/can/vcan.c:44:
> /root/can-isotp-modules/drivers/net/can/vcan.c: In function '__check_echo':
> include/linux/moduleparam.h:377:61: warning: return from incompatible pointer type
> static inline type __always_unused *__check_##name(void) { return(p); }
> ^
> include/linux/moduleparam.h:428:35: note: in expansion of macro '__param_check'
> #define param_check_bool(name, p) __param_check(name, p, bool)
> ^
> include/linux/moduleparam.h:145:2: note: in expansion of macro 'param_check_bool'
> param_check_##type(name, &(value)); \
> ^
> include/linux/moduleparam.h:125:2: note: in expansion of macro 'module_param_named'
> module_param_named(name, name, type, perm)
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3709 bytes --]
next prev parent reply other threads:[~2016-03-30 13:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 5:59 AW: can-isotp-modules Michael Luxen
2016-03-28 9:43 ` can-isotp-modules Patrick Menschel
2016-03-30 12:20 ` can-isotp-modules Oliver Hartkopp
2016-03-30 13:24 ` Patrick Menschel [this message]
2016-03-30 14:54 ` can-isotp-modules Oliver Hartkopp
-- strict thread matches above, loose matches on Subject: below --
2015-11-03 22:29 can-isotp-modules Michael Luxen
2015-11-04 6:59 ` can-isotp-modules Oliver Pajonk
2015-11-04 10:06 ` can-isotp-modules Oliver Hartkopp
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=56FBD37A.2080600@posteo.de \
--to=menschel.p@posteo.de \
--cc=linux-can@vger.kernel.org \
--cc=mluxen@gmx.net \
--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.