All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Pfaff <blp@nicira.com>
To: Thomas Graf <tgraf@redhat.com>
Cc: jesse@nicira.com, dev@openvswitch.org, netdev@vger.kernel.org,
	dborkman@redhat.com, ffusco@redhat.com, fleitner@redhat.com,
	xiyou.wangcong@gmail.com
Subject: Re: [PATCH openvswitch v2] netlink: Implement & enable memory mapped netlink i/o
Date: Mon, 2 Dec 2013 14:26:30 -0800	[thread overview]
Message-ID: <20131202222630.GJ15335@nicira.com> (raw)
In-Reply-To: <529D06BF.1010701@redhat.com>

On Mon, Dec 02, 2013 at 11:16:31PM +0100, Thomas Graf wrote:
> >GCC reports:
> >
> >     ../lib/netlink-socket.c: In function 'nl_sock_send_mmap':
> >     ../lib/netlink-socket.c:369:5: error: implicit declaration of function '__ALIGN_KERNEL' [-Werror=implicit-function-declaration]
> >     cc1: all warnings being treated as errors
> 
> Just so we can simplify this process: what's the oldest environment you
> want the code to compile on?

FreeBSD.

This is not a Linux-specific header, it is included on all platforms.
As the comment at the top says:

/* Netlink protocol definitions.
 *
 * Netlink is a message framing format described in RFC 3549 and used heavily
 * in Linux to access the network stack.  Open vSwitch uses AF_NETLINK sockets
 * for this purpose on Linux.  But on all platforms, Open vSwitch uses Netlink
 * message framing internally for certain purposes.
 *
 * This header provides access to the Netlink message framing definitions
 * regardless of platform.  On Linux, it includes the proper headers directly;
 * on other platforms it directly defines the structures and macros itself.
 */

      reply	other threads:[~2013-12-02 22:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30 12:27 [PATCH openvswitch v2] netlink: Implement & enable memory mapped netlink i/o Thomas Graf
2013-12-02 21:23 ` Ben Pfaff
2013-12-02 22:16   ` Thomas Graf
2013-12-02 22:26     ` Ben Pfaff [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=20131202222630.GJ15335@nicira.com \
    --to=blp@nicira.com \
    --cc=dborkman@redhat.com \
    --cc=dev@openvswitch.org \
    --cc=ffusco@redhat.com \
    --cc=fleitner@redhat.com \
    --cc=jesse@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@redhat.com \
    --cc=xiyou.wangcong@gmail.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 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.