netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 4/6] build: tag function headers rather than decls as exported
Date: Fri, 19 Nov 2010 12:09:45 +0100	[thread overview]
Message-ID: <4CE65AF9.9090904@netfilter.org> (raw)
In-Reply-To: <1289907814-32706-5-git-send-email-jengelh@medozas.de>

I like this patchset. Some minor glitch:

On 16/11/10 12:43, Jan Engelhardt wrote:
> @@ -49,31 +43,31 @@ MNL_API int mnl_socket_getsockopt(const struct mnl_socket *nl, int type, void *b
>  #define MNL_ALIGN(len)		(((len)+MNL_ALIGNTO-1) & ~(MNL_ALIGNTO-1))
>  #define MNL_NLMSG_HDRLEN	MNL_ALIGN(sizeof(struct nlmsghdr))
>  
> -MNL_API size_t mnl_nlmsg_size(size_t len);
> -MNL_API size_t mnl_nlmsg_total_size(size_t len);
> -MNL_API size_t mnl_nlmsg_get_payload_len(const struct nlmsghdr *nlh);
> +extern size_t mnl_nlmsg_size(size_t len);
> +extern size_t mnl_nlmsg_total_size(size_t len);
> +extern size_t mnl_nlmsg_get_payload_len(const struct nlmsghdr *nlh);
>  
>  /* Netlink message header builder */
> -MNL_API struct nlmsghdr *mnl_nlmsg_put_header(void *buf);
> -MNL_API void *mnl_nlmsg_put_extra_header(struct nlmsghdr *nlh, size_t size);
> +extern struct nlmsghdr *mnl_nlmsg_put_header(void *buf);
> +extern void *mnl_nlmsg_put_extra_header(struct nlmsghdr *nlh, size_t size);
>  
>  /* Netlink message iterators */
> -MNL_API bool mnl_nlmsg_ok(const struct nlmsghdr *nlh, int len);
> -MNL_API struct nlmsghdr *mnl_nlmsg_next(const struct nlmsghdr *nlh, int *len);
> +extern bool mnl_nlmsg_ok(const struct nlmsghdr *nlh, int len);
> +extern struct nlmsghdr *mnl_nlmsg_next(const struct nlmsghdr *nlh, int *len);

In patch 1/6 mnl_nlmsg_next looks like:

-struct nlattr *mnl_attr_next(const struct nlattr *attr, int *len)
+struct nlattr *mnl_attr_next(const struct nlattr *attr)

but here the old API seems to come back:

extern struct nlmsghdr *mnl_nlmsg_next(const struct nlmsghdr *nlh, int
*len);

  reply	other threads:[~2010-11-19 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 11:43 libmnl: proposed patches 20101116 Jan Engelhardt
2010-11-16 11:43 ` [PATCH 1/6] attr: avoid multiple definition of hidden variable Jan Engelhardt
2010-11-16 11:43 ` [PATCH 2/6] socket: propagate sendto/recvmsg's return types Jan Engelhardt
2010-11-16 11:43 ` [PATCH 3/6] Update .gitignore Jan Engelhardt
2010-11-16 11:43 ` [PATCH 4/6] build: tag function headers rather than decls as exported Jan Engelhardt
2010-11-19 11:09   ` Pablo Neira Ayuso [this message]
2010-11-19 11:26     ` Jan Engelhardt
2010-11-19 11:43       ` Pablo Neira Ayuso
2010-11-16 11:43 ` [PATCH 5/6] build: add some more precautionary CFLAGS Jan Engelhardt
2010-11-16 11:43 ` [PATCH 6/6] nlmsg: remove unused function Jan Engelhardt
2010-11-19 11:16 ` libmnl: proposed patches 20101116 Pablo Neira Ayuso

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=4CE65AF9.9090904@netfilter.org \
    --to=pablo@netfilter.org \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    /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).