From: David Miller <davem@davemloft.net>
To: nm127@freemail.hu
Cc: socketcan@hartkopp.net, eric.dumazet@gmail.com,
oliver.hartkopp@volkswagen.de, urs.thuermann@volkswagen.de,
socketcan-core@lists.berlios.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.34-rc3 + CAN build problem
Date: Sat, 10 Apr 2010 22:16:18 -0700 (PDT) [thread overview]
Message-ID: <20100410.221618.226789099.davem@davemloft.net> (raw)
In-Reply-To: <4BC15AC7.3010904@freemail.hu>
From: Németh Márton <nm127@freemail.hu>
Date: Sun, 11 Apr 2010 07:14:47 +0200
> David Miller wrote:
>> From: Oliver Hartkopp <socketcan@hartkopp.net>
>> Date: Sat, 10 Apr 2010 14:36:48 +0200
>>
>>> So i wonder why Nemeth trapped into this problem ... probably an include file
>>> mix-up?
>>
>> Do you have CONFIG_DEBUG_STRICT_USER_COPY_CHECKS enabled in your
>> kernel config?
>
> CONFIG_DEBUG_STRICT_USER_COPY_CHECKS=y
Just turn that off in your builds, it's for developers who want
to work on correcting those warnings, not you :-)
next prev parent reply other threads:[~2010-04-11 5:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 8:13 Linux 2.6.34-rc3 + CAN build problem Németh Márton
2010-04-10 9:47 ` Eric Dumazet
2010-04-10 10:36 ` Németh Márton
[not found] ` <4BC054AE.7040303-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
2010-04-10 12:36 ` Oliver Hartkopp
2010-04-10 22:50 ` David Miller
2010-04-11 5:14 ` Németh Márton
2010-04-11 5:16 ` David Miller [this message]
[not found] ` <20100410.155009.66184583.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2010-04-11 18:53 ` Oliver Hartkopp
2010-04-11 20:19 ` David Miller
2010-04-10 22:48 ` David Miller
2010-04-13 10:09 ` David Miller
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=20100410.221618.226789099.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nm127@freemail.hu \
--cc=oliver.hartkopp@volkswagen.de \
--cc=socketcan-core@lists.berlios.de \
--cc=socketcan@hartkopp.net \
--cc=urs.thuermann@volkswagen.de \
/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).