From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Brian Thorne <hardbyte@gmail.com>, linux-can@vger.kernel.org
Subject: Re: [PATCH can-next] Add broadcast manager documentation
Date: Tue, 15 Oct 2013 06:57:32 +0200 [thread overview]
Message-ID: <525CCB3C.8050609@hartkopp.net> (raw)
In-Reply-To: <525C4DC0.5030107@pengutronix.de>
On 14.10.2013 22:02, Marc Kleine-Budde wrote:
> On 10/14/2013 09:41 PM, Oliver Hartkopp wrote:
>> + configuration message is defined. The basic BCM configuration message used
>> + to communicate with the broadcast manager and the available operations are
>> + defined in the linux/can/bcm.h include. The BCM message consists of a
>
> Nitpick
> It's "include/uapi/linux/can/bcm.h" in recent kernel trees.
>
AFAIK the uapi directory is the place where the 'user API' relevant header
files are /generated/ at build time. Finally these header files are copied to
/usr/include/linux/...
in the different Linux distributions to be accessed by application developers.
So in the application C code it's still:
#include <linux/can.h>
#include <linux/can/raw.h>
#include <linux/can/bcm.h>
Right?
Regards,
Oliver
next prev parent reply other threads:[~2013-10-15 4:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 0:56 [PATCH] Broadcast manager documentation Brian Thorne
2013-10-08 8:24 ` Oliver Hartkopp
2013-10-08 14:03 ` Marc Kleine-Budde
2013-10-14 19:41 ` [PATCH can-next] Add broadcast " Oliver Hartkopp
2013-10-14 20:02 ` Marc Kleine-Budde
[not found] ` <CAENe87q9PCCJjgzDp-D7GfhJkGeBJU6kog+YuMHKkNbacg1bTA@mail.gmail.com>
2013-10-14 21:00 ` Brian Thorne
2013-10-15 4:57 ` Oliver Hartkopp [this message]
2013-10-15 7:20 ` Marc Kleine-Budde
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=525CCB3C.8050609@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=hardbyte@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.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 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.