From: Johannes Berg <johannes@sipsolutions.net>
To: Filipe Brandenburger <filbranden@google.com>,
Arik Nemtsov <arik@wizery.com>
Cc: linux-wireless@vger.kernel.org, Elliott Hughes <enh@google.com>,
Christopher Wiley <wiley@google.com>
Subject: Re: [PATCH 0/2] iw: fixes to Android.mk to include "iw" in AOSP builds
Date: Thu, 13 Aug 2015 11:01:24 +0200 [thread overview]
Message-ID: <1439456484.2114.6.camel@sipsolutions.net> (raw)
In-Reply-To: <1438292115-39495-1-git-send-email-filbranden@google.com> (sfid-20150730_233636_420641_73AD4AC6)
On Thu, 2015-07-30 at 14:35 -0700, Filipe Brandenburger wrote:
> Hi,
>
> I'm working on including "iw" on Android AOSP eng builds and it turns
> out we
> need some fixes to Android.mk to make it build on a current AOSP
> tree.
>
We have a very similar patch internally as well (that I was still
evualating/reviewing) but it was less complete, so I've applied this
despite Arik's objections.
I think that if anyone needs to build against older Android, which is
very well possible, we can partially revert this and maybe provide some
environment variable they can control from their BSP, but until
somebody really shows up with that I'll leave it as is and assume that
older Android builds will also use older iw.
johannes
next prev parent reply other threads:[~2015-08-13 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 21:35 [PATCH 0/2] iw: fixes to Android.mk to include "iw" in AOSP builds Filipe Brandenburger
2015-07-30 21:35 ` [PATCH 1/2] iw: fix references to libnl in Android.mk Filipe Brandenburger
2015-07-30 21:36 ` enh
2015-07-30 21:47 ` [PATCH v2 " Filipe Brandenburger
2015-07-31 6:55 ` Arik Nemtsov
2015-07-30 21:35 ` [PATCH 2/2] iw: remove android-nl.c with unneeded workaround Filipe Brandenburger
2015-07-31 6:56 ` Arik Nemtsov
2015-07-31 16:01 ` enh
2015-08-02 6:57 ` Arik Nemtsov
2015-08-02 16:11 ` enh
2015-08-13 9:01 ` Johannes Berg [this message]
2015-08-13 16:55 ` [PATCH 0/2] iw: fixes to Android.mk to include "iw" in AOSP builds Filipe Brandenburger
2015-08-13 18:33 ` Johannes Berg
2015-08-13 19:48 ` enh
2015-08-13 20:01 ` Johannes Berg
2015-08-13 20:44 ` enh
2015-08-13 20:47 ` Johannes Berg
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=1439456484.2114.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arik@wizery.com \
--cc=enh@google.com \
--cc=filbranden@google.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wiley@google.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;
as well as URLs for NNTP newsgroup(s).