All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Bluetooth: Add HCI init setup stage
Date: Thu, 4 Apr 2013 11:24:36 +0300	[thread overview]
Message-ID: <20130404082436.GA2340@x220> (raw)
In-Reply-To: <1364923287-25935-1-git-send-email-johan.hedberg@gmail.com>

Hi,

On Tue, Apr 02, 2013, Johan Hedberg wrote:
> This is a resend of Marcel's patches that were sent in November, rebased
> and fixed-up for bluetooth-next. They are a pre-requsite of some
> follow-up work I'm doing to have a simple way of doing synchronous
> single-command requests that will be needed by some HCI driver setup
> routines.
> 
> Johan
> 
> ----------------------------------------------------------------
> Marcel Holtmann (3):
>       Bluetooth: Add driver setup stage for early init
>       Bluetooth: Convert BCM92035 support to driver setup callback
>       Bluetooth: Remove driver init queue from core
> 
>  drivers/bluetooth/btusb.c        |   28 +++++++++++--------
>  include/net/bluetooth/hci_core.h |    3 +-
>  net/bluetooth/hci_core.c         |   56 ++++++++++++++------------------------
>  3 files changed, 38 insertions(+), 49 deletions(-)

There patches have now been pushed to the bluetooth-next tree.

Johan

  parent reply	other threads:[~2013-04-04  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 17:21 [PATCH v2 0/3] Bluetooth: Add HCI init setup stage Johan Hedberg
2013-04-02 17:21 ` [PATCH v2 1/3] Bluetooth: Add driver setup stage for early init Johan Hedberg
2013-04-02 17:21 ` [PATCH v2 2/3] Bluetooth: Convert BCM92035 support to driver setup callback Johan Hedberg
2013-04-02 17:21 ` [PATCH v2 3/3] Bluetooth: Remove driver init queue from core Johan Hedberg
2013-04-04  8:24 ` Johan Hedberg [this message]
2013-04-04  9:46   ` [PATCH v2 0/3] Bluetooth: Add HCI init setup stage Johan Hedberg
2013-04-04 15:22     ` 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=20130404082436.GA2340@x220 \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.