public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Olivier Le Pogam" <olepogam@free.fr>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Patch mh3
Date: Mon, 1 Oct 2007 16:50:47 +0200	[thread overview]
Message-ID: <004601c8043a$73fcc9e0$0200a8c0@jester> (raw)
In-Reply-To: 1191248069.6484.107.camel@aeonflux.holtmann.net

Hi Marcel,

Thanks a lot, indeed it's really simple :)
Is there a way to have all of these changes applied to my current kernel 
version, or should I simply wait for a next kernel release ?

Best regards,
Oli
----- Original Message ----- 
From: "Marcel Holtmann" <marcel@holtmann.org>
To: "Olivier Le Pogam" <olepogam@free.fr>; "BlueZ development" 
<bluez-devel@lists.sourceforge.net>
Sent: Monday, October 01, 2007 4:14 PM
Subject: Re: [Bluez-devel] Patch mh3


> Hi Olivier,
>
>> I have a 2.6.22.12 kernel (ubuntu gutsy gibbon) and when I want to apply 
>> the
>> mh3 kernel patch (dry run for now) it seems there are some modifications
>> which have already been applied (partially ?) in hci_core.h, rfcomm.h, 
>> sco.h
>
> the patch name is patch-2.6.22-mh3. This means it applies to 2.6.22 and
> might not apply to 2.6.22.12. Otherwise it would have been named
> patch-2.6.22.12-mh3. It is as simple as that.
>
> Regards
>
> Marcel
>
>
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.488 / Virus Database: 269.13.35/1040 - Release Date: 
> 30/09/2007 21:01
> 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-10-01 14:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 13:12 [Bluez-devel] Multiple Bluetooth Dongles Williams, Richard
2007-08-23 20:40 ` Jeffrey Cuenco
2007-08-24 12:13   ` Marcel Holtmann
2007-08-24 14:06   ` [Bluez-devel] multithreaded name resolution Matthias Becker
2007-08-24 12:14     ` Peter Wippich
2007-10-01 13:40       ` [Bluez-devel] [PATCH]Re: " Andreas Gaufer
2007-10-01 14:12         ` [Bluez-devel] Patch mh3 Olivier Le Pogam
2007-10-01 14:14           ` Marcel Holtmann
2007-10-01 14:50             ` Olivier Le Pogam [this message]
2007-10-01 15:56               ` Marcel Holtmann
2007-10-01 16:55           ` Mats Erik Andersson
2007-10-11 11:10         ` [Bluez-devel] [PATCH]Re: multithreaded name resolution Matthias Becker
2007-08-24 12:14 ` [Bluez-devel] Multiple Bluetooth Dongles Marcel Holtmann
2007-08-24 14:08   ` Williams, Richard
2007-08-24 14:25     ` Marcel Holtmann
2007-08-24 15:06       ` Williams, Richard

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='004601c8043a$73fcc9e0$0200a8c0@jester' \
    --to=olepogam@free.fr \
    --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