linux-wpan.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: jiri@resnulli.us
Subject: Re: [PATCHv2 wpan-tools 1/6] nl_extras: initial commit for extra nl bindings
Date: Sat, 6 Sep 2014 10:17:05 +0200	[thread overview]
Message-ID: <20140906081703.GA19201@omega> (raw)
In-Reply-To: <1409823174-22491-2-git-send-email-alex.aring@gmail.com>

Hi Jiri Pirko,

I need a special header for my netlink application for introduce the
signed integer types, which are not in current release of libnl.

First I took the headr from [0].
Then I saw it's LGPL, to avoid any code license issues I reimplement it
now in my own header. It really looks the same, but putting my application
to LGPL is out of question.

Now I want to be sure that you don't see a copy&paste and remove the license.
Please let me know if this is okay for you.

- Alex

[0] https://github.com/jpirko/libteam/blob/master/libteam/nl_updates.h

On Thu, Sep 04, 2014 at 11:32:49AM +0200, Alexander Aring wrote:
> This header file is needed for additional signed bindings which are not
> in netlink library, currently.
> 
> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> ---
>  src/nl_extras.h | 36 ++++++++++++++++++++++++++++++++++++
>  1 file changed, 36 insertions(+)
>  create mode 100644 src/nl_extras.h
> 
> diff --git a/src/nl_extras.h b/src/nl_extras.h
> new file mode 100644
> index 0000000..39a97c6
> --- /dev/null
> +++ b/src/nl_extras.h
> @@ -0,0 +1,36 @@
> +#ifndef __NL_EXTRAS_H
> +#define __NL_EXTRAS_H
> +
> +#ifndef NLA_S8
> +
> +#define NLA_S8	13
> +#define NLA_PUT_S8(n, attrtype, value) \
> +	NLA_PUT_TYPE(n, int8_t, attrtype, value)
> +
> +#endif /* NLA_S8 */
> +
> +#ifndef NLA_S16
> +
> +#define NLA_S16	14
> +#define NLA_PUT_S16(n, attrtype, value) \
> +	NLA_PUT_TYPE(n, int16_t, attrtype, value)
> +
> +#endif /* NLA_S16 */
> +
> +#ifndef NLA_S32
> +
> +#define NLA_S32	15
> +#define NLA_PUT_S32(n, attrtype, value) \
> +	NLA_PUT_TYPE(n, int32_t, attrtype, value)
> +
> +#endif /* NLA_S32 */
> +
> +#ifndef NLA_S64
> +
> +#define NLA_S64	16
> +#define NLA_PUT_S64(n, attrtype, value) \
> +	NLA_PUT_TYPE(n, int64_t, attrtype, value)
> +
> +#endif /* NLA_S64 */
> +
> +#endif /* __NL_EXTRAS_H */
> -- 
> 2.1.0
> 

  reply	other threads:[~2014-09-06  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04  9:32 [PATCHv2 wpan-tools 0/6] wpan-tools: new netlink interfaces calls Alexander Aring
2014-09-04  9:32 ` [PATCHv2 wpan-tools 1/6] nl_extras: initial commit for extra nl bindings Alexander Aring
2014-09-06  8:17   ` Alexander Aring [this message]
2014-09-04  9:32 ` [PATCHv2 wpan-tools 2/6] phy: add support for tx power pib attribute Alexander Aring
2014-09-04  9:32 ` [PATCHv2 wpan-tools 3/6] phy: add support for setting cca_mode Alexander Aring
2014-09-04  9:32 ` [PATCHv2 wpan-tools 4/6] mac: add support for setting max_frame_retries Alexander Aring
2014-09-04  9:32 ` [PATCHv2 wpan-tools 5/6] mac: initial support for setting csma params Alexander Aring
2014-09-04  9:32 ` [PATCHv2 wpan-tools 6/6] phy: add support for cca mode 3 and/or handling Alexander Aring

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=20140906081703.GA19201@omega \
    --to=alex.aring@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=linux-wpan@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).