From: Max Krasnyansky <maxk@qualcomm.com>
To: david.libault@inventel.fr, "Daryl Van Vorst" <dvpub@telus.net>,
<bluez-devel@lists.sourceforge.net>
Cc: Halam.Rose@7layers-UK.com
Subject: Re: [Bluez-devel] BlueZ Qualification
Date: Fri, 28 Feb 2003 12:46:21 -0800 [thread overview]
Message-ID: <5.1.0.14.2.20030228122906.023b3ca8@mail1.qualcomm.com> (raw)
In-Reply-To: <3E26CE210187508B@mel-rta6.wanadoo.fr> (added by postmaster@wanadoo.fr)
At 01:01 AM 2/28/2003, David LIBAULT wrote:
>Max, can you "coordinate the efforts" for qualification ?
I probably could. But I don't want to because I won't be very effective at it.
Mostly because of lack of time. When I do get free time I'd rather
fix bugs and implement missing features.
So I'd prefer if somebody else will lead and coordinate the efforts.
>Who is going to write the test report ?
>Is Bluez going to be listed as official Bluetooth qualified stack ?
I don't know. That's what we need to discuss.
There are many questions (at least in my mind) like
- Does it make sense to have qualified stack in the official kernel ?
Like I mentioned before I don't want to add things that simply don't make
sense for general stack operation only because we want to pass qualification
(I'm talking mostly about kernel stuff here).
In which case a separate qualified kernel package with the same API as mainstream
kernel make sense.
- What happens when we make changes to the stack ? Have to qualify again ?
etc
Max
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-02-28 20:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 0:27 [Bluez-devel] BlueZ Qualification Daryl Van Vorst
2003-02-27 21:09 ` Max Krasnyansky
2003-02-28 9:01 ` David LIBAULT
2003-02-28 9:38 ` Marcel Holtmann
2003-02-28 10:49 ` BlueZ Qualification and 7 Layers UK Halam Rose
2003-02-28 11:10 ` [Bluez-devel] " David LIBAULT
2003-02-28 20:58 ` Max Krasnyansky
2003-03-03 16:03 ` Marcel Holtmann
2003-02-28 20:48 ` [Bluez-devel] BlueZ Qualification Max Krasnyansky
2003-02-28 20:28 ` Max Krasnyansky
2003-02-28 20:46 ` Max Krasnyansky [this message]
2003-03-03 15:48 ` Marcel Holtmann
2003-03-03 18:06 ` David LIBAULT
2003-03-06 22:06 ` Max Krasnyansky
2003-03-07 8:47 ` David LIBAULT
2003-03-07 17:44 ` Max Krasnyansky
2003-03-25 1:51 ` Max Krasnyansky
2003-03-05 4:35 ` Takashi Sasai
2003-03-06 22:11 ` Max Krasnyansky
2003-03-06 21:33 ` Max Krasnyansky
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=5.1.0.14.2.20030228122906.023b3ca8@mail1.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=Halam.Rose@7layers-UK.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=david.libault@inventel.fr \
--cc=dvpub@telus.net \
/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