All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: enh <enh@google.com>
Cc: Filipe Brandenburger <filbranden@google.com>,
	Arik Nemtsov <arik@wizery.com>,
	linux-wireless@vger.kernel.org,
	Christopher Wiley <wiley@google.com>,
	Ying Wang <wangying@google.com>
Subject: Re: [PATCH 0/2] iw: fixes to Android.mk to include "iw" in AOSP builds
Date: Thu, 13 Aug 2015 22:47:16 +0200	[thread overview]
Message-ID: <1439498836.2114.41.camel@sipsolutions.net> (raw)
In-Reply-To: <CAJgzZoqQ=QP37k+7M_tW2HTeL_HB6YqiUsFC8eUHaGPFGPa6pA@mail.gmail.com> (sfid-20150813_224441_410819_2A37613E)

On Thu, 2015-08-13 at 13:44 -0700, enh wrote:

> but given that our iw is your iw anyway... i don't understand the
> situation in which they'd be inconvenienced here?
> 

But it's not. We can reasonably expect everyone who actually cares to
have local modifications to iw that they aren't publishing (and that I
wouldn't apply anyway since it'd be for vendor commands) - and they
need to build *that* iw, not "our" iw.

The fact that libwifihal more or less wants you to do vendor extensions
makes that all the more likely, since if you want to test those with iw
then you need a modified iw.

johannes

      reply	other threads:[~2015-08-13 20:47 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 ` [PATCH 0/2] iw: fixes to Android.mk to include "iw" in AOSP builds Johannes Berg
2015-08-13 16:55   ` 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 [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=1439498836.2114.41.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=wangying@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.