public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Steffen Becker <steffen.becker@tu-ilmenau.de>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: Re: are those patches up-to-date?
Date: Thu, 24 May 2012 14:02:42 +0200	[thread overview]
Message-ID: <e321504366890477f93366a9af7f3318@localhost> (raw)
In-Reply-To: <20120524101709.GA23856@x220>

Hi Johan,

Johan Hedberg schrieb:
> Hi Steffen,
> 
> On Thu, May 24, 2012, Steffen Becker wrote:
>> I searched a little in your mail archive on gmane and found
>> something that looks similar to my problem. On 25th January 2011 and
>> 26th October 2011 you pushed out two patches because of a security
>> block issue -> "[PATCH] bluetooth: Fix for security block issue."
>> and "[PATCH] Bluetooth: Revert: Fix L2CAP connection establishment".
>>
>> The postet hcidump message in the second mail (10/26/2011) looks
>> very similar to my hcidump message.
>>
>> So I would like to know if those two patches are up-to-date
>> (compatibel with bluez4.99) and/or if they are already included in
>> bluez4.99 (so patching is not necessary) ?
> 
> Your question doesn't make much sense as those are both kernel patches
> and BlueZ 4.99 is a user space component. I think both of those patches
> can be found in kernel 3.3 and later.
> 
> Johan

Oh thanks, I'm new to linux so my comprehension isn't that well.
But are you sure with "kernel 3.3" ?
Because I have gentoo-3.2.12 and thought this is the latest version...

  reply	other threads:[~2012-05-24 12:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  9:56 are those patches up-to-date? Steffen Becker
2012-05-24 10:17 ` Johan Hedberg
2012-05-24 12:02   ` Steffen Becker [this message]
2012-05-24 12:40     ` Andrei Emeltchenko

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=e321504366890477f93366a9af7f3318@localhost \
    --to=steffen.becker@tu-ilmenau.de \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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