linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org, ville.tervo@nokia.com
Subject: Re: [PATCH 0/5] Fixes for authentication and security level issues
Date: Wed, 19 Jan 2011 12:24:25 +0100	[thread overview]
Message-ID: <1295436265.3873.239.camel@aeonflux> (raw)
In-Reply-To: <1295419012-25717-1-git-send-email-johan.hedberg@gmail.com>

Hi Johan,

> Here's a set of patches that we created based on a recent test-run with
> the BITE tester. They should be fine, but we're still re-running all GAP
> and L2CAP tests during today to see that there aren't any regressions.

besides the typo, I can't spot anything wrong with these patches. So
depending on that these pass BITE testing.

Acked-by: Marcel Holtmann <marcel@holtmann.org>

Regards

Marcel



      parent reply	other threads:[~2011-01-19 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19  6:36 [PATCH 0/5] Fixes for authentication and security level issues johan.hedberg
2011-01-19  6:36 ` [PATCH 1/5] Revert "Bluetooth: Update sec_level/auth_type for already existing connections" johan.hedberg
2011-01-19  6:49   ` Johan Hedberg
2011-01-19  6:36 ` [PATCH 2/5] Bluetooth: Fix MITM protection requirement preservation johan.hedberg
2011-01-19  6:36 ` [PATCH 3/5] Bluetooth: Create a unified auth_type evaluation function johan.hedberg
2011-01-19  6:36 ` [PATCH 4/5] Bluetooth: Fix authentication request for L2CAP raw sockets johan.hedberg
2011-01-19 16:29   ` Gustavo F. Padovan
2011-01-19  6:36 ` [PATCH 5/5] Bluetooth: Fix race condition with conn->sec_level johan.hedberg
2011-01-19 16:44   ` Gustavo F. Padovan
2011-01-19 11:24 ` 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=1295436265.3873.239.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ville.tervo@nokia.com \
    /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).