public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Bin <binch@mobilesoft.com.cn>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Prepare patch bluez for the CoD in hci_conn
Date: Tue, 07 Dec 2004 01:40:46 +0800	[thread overview]
Message-ID: <1102354847.2296.3.camel@debian> (raw)
In-Reply-To: <1102323875.8510.78.camel@pegasus>

=D4=DA 2004-12-06=D2=BB=B5=C4 10:04 +0100=A3=ACMarcel Holtmann=D0=B4=B5=C0=
=A3=BA
> Hi Chen,
>=20
> > Ok, use your patch is ok, if I have find some more info in the Blueto=
oth
> > Spec, I will send my patch to you:)
>=20
> it is only compile tested, but actually from a code review it should do
> exactly what was requested. If you wanna test it, you must change the
> ie->data into ie->info, because the inquiry_data change is not yet
> merged back into mainline. A new -mh patch will follow soon.
>=20

I have test my patch, and I will test yours too.=20

And I wanna know which kernel version you current work on? Your new -mh
patch will only apply to the newest kernel or olders too?

I don't know much about your patch convention.

> > BTW: I will remain our company's BT engineer and if the BlueZ have so=
me
> > part not completed, may be I can contribute to do some work:)
>=20
> Go ahead, because every patch is welcome.
>=20
> Regards
>=20
> Marcel
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users=
.
> Discover which products truly live up to the hype. Start reading now.=20
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-12-06 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 13:34 [Bluez-devel] Prepare patch bluez for the CoD in hci_conn Chen Bin
2004-12-06  6:40 ` Marcel Holtmann
2004-12-06 15:11   ` Chen Bin
2004-12-06  7:18     ` Marcel Holtmann
2004-12-06 15:50       ` Chen Bin
2004-12-06  8:07         ` Marcel Holtmann
2004-12-06 15:53       ` Chen Bin
2004-12-06  8:41         ` Marcel Holtmann
2004-12-06 16:54           ` Chen Bin
2004-12-06  9:04             ` Marcel Holtmann
2004-12-06 17:40               ` Chen Bin [this message]
2004-12-06  9:56                 ` Marcel Holtmann
2004-12-06 17:05           ` Chen Bin
2004-12-06  9:14             ` Marcel Holtmann
2004-12-06 17:21               ` Chen Bin

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=1102354847.2296.3.camel@debian \
    --to=binch@mobilesoft.com.cn \
    --cc=bluez-devel@lists.sourceforge.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