All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: pacho@condmat1.ciencias.uniovi.es
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Make the path to oui.txt a compile-time option
Date: Mon, 06 Sep 2010 16:22:36 +0100	[thread overview]
Message-ID: <1283786557.7529.26.camel@localhost.localdomain> (raw)
In-Reply-To: <1283786212.28657.3.camel@localhost.localdomain>

On Mon, 2010-09-06 at 17:16 +0200, Pacho Ramos wrote:
> El lun, 06-09-2010 a las 16:15 +0100, Bastien Nocera escribió:
> > On Mon, 2010-09-06 at 17:12 +0200, Pacho Ramos wrote:
> > > El lun, 06-09-2010 a las 15:47 +0100, Bastien Nocera escribió:
> > > > Heya,
> > > > 
> > > > We've been carrying a similar (but hard-coded) patch in Fedora for a
> > > > long while, and it would be nice if we could do this properly upstream
> > > > instead.
> > > > 
> > > > Patch attached with explanations.
> > > > 
> > > > Cheers
> > > 
> > > What is the proper package to ship oui.txt file? Thanks a lot for the
> > > information :-)
> > 
> > No idea. In Fedora we ship it in hwdata. No idea where it lives for
> > Debian-based distributions, or others.
> > 
> 
> OK, thanks, I asked it because under Gentoo no package is currently
> providing it and a user suggested to supply it with bluez... but I
> haven't made any decision about this yet

That's probably a good enough way to ship it. Various distributions seem
to have a different idea on where it should be.


  reply	other threads:[~2010-09-06 15:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06 14:47 [PATCH] Make the path to oui.txt a compile-time option Bastien Nocera
2010-09-06 15:12 ` Pacho Ramos
2010-09-06 15:15   ` Bastien Nocera
2010-09-06 15:16     ` Pacho Ramos
2010-09-06 15:22       ` Bastien Nocera [this message]
2010-09-06 15:38         ` Pacho Ramos
2010-09-06 16:10 ` Johan Hedberg

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=1283786557.7529.26.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pacho@condmat1.ciencias.uniovi.es \
    /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.