netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Bluetooth fixes for 2.6.27
Date: Tue, 09 Sep 2008 06:46:01 +0200	[thread overview]
Message-ID: <1220935561.13336.2.camel@californication> (raw)
In-Reply-To: <20080908.213050.176981752.davem@davemloft.net>

Hi Dave,

> > > > The number of users are still limited to a few people actually
> > > > testing with 2.1 hardware. These are mainly people working on 2.1
> > > > enabled products. However with the new MacBooks and the EeePC 901 we
> > > > do have devices with Bluetooth 2.1 chips available for everybody.
> > > >
> > > > This is clearly an oversight on my hand when developing the initial
> > > > Simple Pairing patches that I submitted for 2.6.27-rc1 and I only
> > > > found it when we tested against the official Bluetooth 2.1 test
> > > > system.
> > > 
> > > This is the core issue, if it regresses from 2.6.26, and if so you should
> > > mention that somewhere.  Best would be in the commit message itself.
> > > 
> > > Then I wouldn't have had to ask you anything.
> > > 
> > > But instead you're having to describe it for me here in this email, which
> > > nobody can see when scanning the GIT commit messages, so it essentially
> > > might as well not even exist.
> > 
> > I thought that I did describe this properly in the commit message, but
> > it could also only be clear to me. Do you want me to fix up the commit
> > message with more details?
> 
> Where in your commit message did you specifically state and explain
> that this problem is specifically a regression against 2.6.26?  I didn't
> catch that part.

it was the "... L2CAP PSM 1 (used by SDP) the just-works model ..." and
I admit, after you pointing my nose on it, that it is not clear to
anybody not deeply into this Bluetooth 2.1 stuff.

Let me fix up the tree and have this commit with a better explanation
what it is all about.

Regards

Marcel



  reply	other threads:[~2008-09-09  4:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 21:53 Bluetooth fixes for 2.6.27 Marcel Holtmann
2008-09-09  0:05 ` David Miller
2008-09-09  2:04   ` Marcel Holtmann
2008-09-09  2:42     ` David Miller
2008-09-09  4:28       ` Marcel Holtmann
2008-09-09  4:30         ` David Miller
2008-09-09  4:46           ` Marcel Holtmann [this message]
2008-09-09  4:48             ` David Miller
2008-09-09  6:08               ` Marcel Holtmann
2008-09-09 10:02                 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2008-08-19  8:23 Marcel Holtmann
2008-08-19  8:38 ` David Miller

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=1220935561.13336.2.camel@californication \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).