Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Plugz SCO Patches submitted to the kernel	developers?
Date: Sat, 31 Mar 2007 15:35:15 +0200	[thread overview]
Message-ID: <1175348115.5815.242.camel@violet> (raw)
In-Reply-To: <5FD5754DDBA0B1499B5A0B4BB5419485D44D28@fmsmsx411.amr.corp.intel.com>

Hi Mark,

> Have the plugz SCO kernel patches (sco-flowcontrol-v3.0.diff) beed
> submitted to the kernel team
> so that it can be included in the upstream kernel? If so, do we yet
> know which kernel it is
> supposed to be in?

I got a re-worked patch from Brad two weeks ago. This one still needs
testing and some cleanup. However in general this patch is meant to go
upstream.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-03-31 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 23:17 [Bluez-devel] Plugz SCO Patches submitted to the kernel developers? Allyn, Mark A
2007-03-31 13:35 ` Marcel Holtmann [this message]

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=1175348115.5815.242.camel@violet \
    --to=marcel@holtmann.org \
    --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