Linux bluetooth development
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: Takashi Sasai <sasai@sm.sony.co.jp>,
	Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
Cc: david.libault@inventel.fr, Daryl Van Vorst <dvpub@telus.net>,
	bluez-devel@lists.sourceforge.net, Halam.Rose@7layers-UK.com
Subject: Re: [Bluez-devel] BlueZ Qualification
Date: Thu, 06 Mar 2003 14:11:27 -0800	[thread overview]
Message-ID: <5.1.0.14.2.20030306140737.024bc350@mail1.qualcomm.com> (raw)
In-Reply-To: <8765qysa6g.wl@maple.sm.sony.co.jp>

At 08:35 PM 3/4/2003, Takashi Sasai wrote:
>I feel it's good to just confirm core functionarities (l2cap, sdp and gap for me).
That's one of the benefits of qualification effort that for example I as a developer
will get. And if helps companies that make devices based on Linux it's even better.

Max

  reply	other threads:[~2003-03-06 22:11 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
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 [this message]
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.20030306140737.024bc350@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 \
    --cc=marcel@rvs.uni-bielefeld.de \
    --cc=sasai@sm.sony.co.jp \
    /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