Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <Mikko.Rapeli@bmw.de>
To: <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 02/12] hostap-utils: Use C99 stddefs in defining local typedefs
Date: Wed, 16 Sep 2015 06:01:08 +0000	[thread overview]
Message-ID: <20150916055705.GX9460@loska> (raw)
In-Reply-To: <CAMKF1soOSzDNCTtCk-piCt0LHbrP6p6eZZCE6EuWaf5WHkK2BQ@mail.gmail.com>

On Tue, Sep 15, 2015 at 08:13:26AM -0700, Khem Raj wrote:
> On Mon, Sep 14, 2015 at 11:33 PM,  <Mikko.Rapeli@bmw.de> wrote:
> > On Mon, Sep 14, 2015 at 04:31:17PM +0000, Khem Raj wrote:
> >> The code is creating more abstract types which is nice however it should
> >> be using standard defines from stdint.h and not random defines to base
> >> its own type system
> >
> > These types are not random. They are standard Linux kernel types used by headers
> > exported to userspace and their definitions come from <linux/types.h>.
> > These headers should not depend on libc headers like stdint.h.
> 
> Right they are not random in general but they are randomly being
> redefined by the application,
> if it should be using linux/types.h those are different types than
> what is being defined here. I have just
> made the semantics of existing logic to be more c99 compliant.
> 
> >
> > Also, this file is actually a convenience copy of <linux/wireless.h> which should
> > be used directly instead.
> 
> There must be a reason to make own copy. May be hostap-utils want to
> be portable to more than linux

A private copy of <linux/wireless.h> is only usefull with Linux kernel. Since
mid 2000's Linux kernel has a way to properly export these headers to
userspace. Thus the private copies should not be needed anymore.

-Mikko

  reply	other threads:[~2015-09-16  6:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 16:31 [PATCH 00/12] Fixes with clang Khem Raj
2015-09-14 16:31 ` [PATCH 01/12] xz: Correctly specify GPL-3.0 with autoconf exception Khem Raj
2015-09-14 16:31 ` [PATCH 02/12] hostap-utils: Use C99 stddefs in defining local typedefs Khem Raj
2015-09-15  6:33   ` Mikko.Rapeli
2015-09-15 15:13     ` Khem Raj
2015-09-16  6:01       ` Mikko.Rapeli [this message]
2015-09-14 16:31 ` [PATCH 03/12] xorg-driver: Fix logical && with bitwise and operation Khem Raj
2015-09-14 16:31 ` [PATCH 04/12] qt4: Fix kmap2qmap build with clang Khem Raj
2015-09-14 16:31 ` [PATCH 05/12] gummiboot: Fix build warnings seen with gcc5 Khem Raj
2015-09-14 16:31 ` [PATCH 06/12] gnu-efi, syslinux: Support gcc < 4.7 Khem Raj
2015-09-14 16:31 ` [PATCH 07/12] syslinux: Dont bypass gcc driver for dependency generation options Khem Raj
2015-09-14 16:31 ` [PATCH 08/12] opkg: Include stdio.h for FILE definition Khem Raj
2015-09-14 16:31 ` [PATCH 09/12] quota: Replace using -I= with STAGING_INCDIR Khem Raj
2015-09-14 16:31 ` [PATCH 10/12] connman: Fix build with musl Khem Raj
2015-09-14 16:31 ` [PATCH 11/12] waffle: upgrade waffle_1.5.1.bb -> waffle_1.5.2.bb Khem Raj
2015-09-18 20:21   ` Burton, Ross
2015-09-18 21:04     ` Khem Raj
2015-09-14 16:31 ` [PATCH 12/12] sysstat: Include needed headers explicitly Khem Raj

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=20150916055705.GX9460@loska \
    --to=mikko.rapeli@bmw.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox