public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Add sixaxis cable-pairing plugin
Date: Fri, 05 Jun 2009 16:06:17 +0100	[thread overview]
Message-ID: <1244214377.30768.2690.camel@cookie.hadess.net> (raw)
In-Reply-To: <1244213775.23850.57.camel@localhost.localdomain>

On Fri, 2009-06-05 at 16:56 +0200, Marcel Holtmann wrote:
> 
> > > On that point, you haven't merged the Socket fix upstream
> > 
> > It's not upstreamable, see the RH bugzilla. It depends on a kernel
> patch
> > that can't go upstream.
> 
> Which bug is it.

It's listed in the spec file, in the same directory you found that
patch:
https://bugzilla.redhat.com/show_bug.cgi?id=498756

>  What is missing and why haven't I seen that kernel
> patch at least send to the mailing list for review.

It's a patch to serial core, not Bluetooth, and there's a 3-year old
discussion on LKML, amongst other things.

  reply	other threads:[~2009-06-05 15:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  9:28 [PATCH] Add sixaxis cable-pairing plugin Bastien Nocera
2009-06-04 18:13 ` Marcel Holtmann
2009-06-05 10:42   ` Bastien Nocera
2009-06-05 13:06     ` Marcel Holtmann
2009-06-05 13:52       ` Bastien Nocera
2009-06-05 14:15         ` Marcel Holtmann
2009-06-05 14:48           ` Bastien Nocera
2009-06-05 14:56             ` Marcel Holtmann
2009-06-05 15:06               ` Bastien Nocera [this message]
2009-06-06 17:41                 ` Luiz Augusto von Dentz
2009-06-06 17:51                   ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2009-10-09 13:19 Bastien Nocera
2009-10-11  9:40 ` Marcel Holtmann

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=1244214377.30768.2690.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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