From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 0/6] batman-adv: Include cleanup
Date: Wed, 06 Dec 2017 11:42:58 +0100 [thread overview]
Message-ID: <14408119.DPNAsOUNfy@bentobox> (raw)
In-Reply-To: <20171119161207.32588-1-sven@narfation.org>
[-- Attachment #1: Type: text/plain, Size: 445 bytes --]
On Sonntag, 19. November 2017 17:12:01 CET Sven Eckelmann wrote:
> Hi,
>
> I went through the build_test.git's testhelpers/kernel_mappings.iwyu and
> cleaned that up a little bit. This requires that we have to adjust the
> batman-adv sources slighty.
>
> I have also found a build problem when you try to build B.A.T.M.A.N. V
> against Linux < 3.7 and fixed it in the same patchset.
Applied in 8de104e049ea..cfcb3be43ef5
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-12-06 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 16:12 [B.A.T.M.A.N.] [PATCH 0/6] batman-adv: Include cleanup Sven Eckelmann
2017-11-19 16:12 ` [B.A.T.M.A.N.] [PATCH 1/6] batman-adv: include gfp.h for GFP_* defines Sven Eckelmann
2017-11-19 16:12 ` [B.A.T.M.A.N.] [PATCH 2/6] batman-adv: include build_bug.h for BUILD_BUG_ON define Sven Eckelmann
2017-11-19 16:12 ` [B.A.T.M.A.N.] [PATCH 3/6] batman-adv: Include net.h for net_ratelimited_function Sven Eckelmann
2017-11-19 16:12 ` [B.A.T.M.A.N.] [PATCH 4/6] batman-adv: include kobject.h for kobject_* functions Sven Eckelmann
2017-11-19 16:12 ` [B.A.T.M.A.N.] [PATCH 5/6] batman-adv: Remove unused sched.h include Sven Eckelmann
2017-11-19 16:12 ` [B.A.T.M.A.N.] [PATCH 6/6] batman-adv: compat: Map to linux/nl80211.h for Linux < 3.7 Sven Eckelmann
2017-12-06 10:42 ` Sven Eckelmann [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=14408119.DPNAsOUNfy@bentobox \
--to=sven@narfation.org \
--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