From: Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Stefan Seyfried <stefan.seyfried@googlemail.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: bluez-hcidump-1.42 fails to build against bluez-4.61
Date: Mon, 08 Mar 2010 14:56:54 +0100 [thread overview]
Message-ID: <1268056614.7822.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1267998239.3712.11.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
El dom, 07-03-2010 a las 13:43 -0800, Marcel Holtmann escribió:
> Hi Stefan,
>
> > > This is for recovering:
> > > http://comments.gmane.org/gmane.linux.bluez.kernel/4619
> > >
> > > since more users are getting this problem and I would like to know if
> > > patches provided in that thread can be used and accepted by upstream or
> > > they are not good enough.
> >
> > In case they only got overlooked, I can of course resend them.
> >
> > If they are not good enough, mentioning the problems might be
> > helpful, so that I can do something about it ;)
>
> they didn't get overlooked. It was my mistake that I broke hcidump and I
> now put everything back in the library. So 4.62 should fix it. I was
> under the assumption that nothing ever used these symbols, but as it
> seems I was clearly wrong. Sorry about that.
>
> Regards
>
> Marcel
>
>
We should then simply wait for bluez-4.62 and, then, no patches would be
needed for bluez-hcidump, not? (or I have missed anything?)
Thanks a lot and best regards :-)
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-08 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 18:48 bluez-hcidump-1.42 fails to build against bluez-4.61 Pacho Ramos
2010-03-05 19:30 ` Stefan Seyfried
2010-03-07 21:43 ` Marcel Holtmann
2010-03-08 13:56 ` Pacho Ramos [this message]
2010-03-08 14:05 ` Stefan Seyfried
2010-03-08 14:36 ` Pacho Ramos
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=1268056614.7822.4.camel@localhost.localdomain \
--to=pacho@condmat1.ciencias.uniovi.es \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=stefan.seyfried@googlemail.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).