public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv4 2/4] batman-adv: Add required to includes to all files
Date: Tue, 21 Apr 2015 11:46:51 +0800	[thread overview]
Message-ID: <1595618.4CGjfVRuAA@voltaire> (raw)
In-Reply-To: <1429292430-30883-2-git-send-email-sven@narfation.org>

[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]

On Friday, April 17, 2015 19:40:28 Sven Eckelmann wrote:
> The header files could not be build indepdent from each other. This is
> happened because headers didn't include the files for things they've used.
> This was problematic because the success of a build depended on the
> knowledge about the right order of local includes.
> 
> Also source files were not including everything they've used explicitly.
> Instead they required that transitive includes are always stable. This is
> problematic because some transitive includes are not obvious, depend on
> config settings and may not be stable in the future.
> 
> The order for include blocks are:
> 
>  * primary headers (main.h and the *.h file of a *.c file)
>  * global linux headers
>  * required local headers
>  * extra forward declarations for pointers in function/struct declarations
> 
> The only exceptions are linux/bitops.h and linux/if_ether.h in packet.h.
> This header file is shared with userspace applications like batctl and must
> therefore build together with userspace applications. The header
> linux/bitops.h is not part of the uapi headers and linux/if_ether.h
> conflicts with the musl implementation of netinet/if_ether.h. The
> maintainers rejected the use of __KERNEL__ preprocessor checks and thus
> these two headers are only in main.h. All files using packet.h first have
> to include main.h to work correctly.
> 
> Reported-by: Markus Pargmann <mpa@pengutronix.de>
> Signed-off-by: Sven Eckelmann <sven@narfation.org>

Applied in revision 960339d.

Thanks,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2015-04-21  3:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 17:40 [B.A.T.M.A.N.] [PATCHv4 1/4] batman-adv: Remove explicit compat.h include and split compat.h Sven Eckelmann
2015-04-17 17:40 ` [B.A.T.M.A.N.] [PATCHv4 2/4] batman-adv: Add required to includes to all files Sven Eckelmann
2015-04-20 16:25   ` Sven Eckelmann
2015-04-21  3:46   ` Marek Lindner [this message]
2015-04-17 17:40 ` [B.A.T.M.A.N.] [PATCHv4 3/4] batman-adv: Remove unused IFF_BRIDGE_PORT live patching hack Sven Eckelmann
2015-04-21  3:48   ` Marek Lindner
2015-04-21  6:04     ` Sven Eckelmann
2015-04-21  8:53       ` Marek Lindner
2015-04-17 17:40 ` [B.A.T.M.A.N.] [PATCHv4 4/4] batman-adv: Automatically create nested kfree_rcu helper functions Sven Eckelmann
2015-04-21  3:52   ` Marek Lindner
2015-04-21  6:35     ` Sven Eckelmann
2015-04-21  9:01       ` Marek Lindner
2015-04-20 16:12 ` [B.A.T.M.A.N.] [PATCHv5 1/4] batman-adv: Remove explicit compat.h include and split compat.h Sven Eckelmann
2015-04-21  3:41 ` [B.A.T.M.A.N.] [PATCHv4 " Marek Lindner
2015-04-21  6:19   ` Sven Eckelmann
2015-04-21  9:02     ` Marek Lindner

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=1595618.4CGjfVRuAA@voltaire \
    --to=mareklindner@neomailbox.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.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