linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Kevin Hayes <kevin@Atheros.com>,
	David Quan <David.Quan@Atheros.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"geoclue@lists.freedesktop.org" <geoclue@lists.freedesktop.org>
Subject: Re: [PATCH 0/2] iw: add GeoClue support
Date: Mon, 23 Aug 2010 15:22:36 -0700	[thread overview]
Message-ID: <20100823222236.GE2206@tux> (raw)
In-Reply-To: <1282601707.3405.140.camel@localhost.localdomain>

On Mon, Aug 23, 2010 at 03:15:07PM -0700, Bastien Nocera wrote:
> On Mon, 2010-08-23 at 15:11 -0700, Luis R. Rodriguez wrote:
> > On Mon, Aug 23, 2010 at 02:05:56PM -0700, Bastien Nocera wrote:
> <snip>
> > > No, I'm talking about what's exported by the providers. I don't really
> > > care if they talk to other parts of the system using D-Bus though. I'm
> > > talking about link 2) here.
> > > 
> > > [App] <-1-> [Geoclue master] <-2-> [Gypsy provider] <-3-> [Gypsy daemon]
> > 
> > Sorry I do not follow yet. Is the idea that you would prefer if
> > client applications would never talk to providers directly and instead
> > always used the master provider?
> 
> Exactly, and it's mentioned in the bugzilla

Thanks for the heads up, I haven't been grep'ing through the bugzilla.

> and was discussed on the mailing-list as well.

And am new there :)

This makes sense -- are there plans on removing all these exported
library routines so that the only exposed thing is the master
provider calls?

Based on your comments it seems changing the iw patch to just
use the master provider would go more in line with current
development focus.

  Luis

  reply	other threads:[~2010-08-23 22:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-21  0:29 [PATCH 0/2] iw: add GeoClue support Luis R. Rodriguez
2010-08-21  0:29 ` [PATCH 1/2] iw: make is_alpha2() available to other objects Luis R. Rodriguez
2010-08-21  0:29 ` [PATCH 2/2] iw: add GeoClue support for automatically determining location Luis R. Rodriguez
2010-08-23 14:11 ` [PATCH 0/2] iw: add GeoClue support Johannes Berg
2010-08-23 15:44   ` Luis R. Rodriguez
2010-08-23 16:05     ` Bastien Nocera
2010-08-23 17:46       ` Luis R. Rodriguez
2010-08-23 21:05         ` Bastien Nocera
2010-08-23 22:11           ` Luis R. Rodriguez
2010-08-23 22:15             ` Bastien Nocera
2010-08-23 22:22               ` Luis R. Rodriguez [this message]
2010-08-23 22:29                 ` Bastien Nocera

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=20100823222236.GE2206@tux \
    --to=lrodriguez@atheros.com \
    --cc=David.Quan@Atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=geoclue@lists.freedesktop.org \
    --cc=hadess@hadess.net \
    --cc=johannes@sipsolutions.net \
    --cc=kevin@Atheros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).