From: Ron Shaffer <rshaffer@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Don't send SCO/eSCO request during a mode change from sniff to active
Date: Fri, 28 May 2010 10:45:31 -0500 [thread overview]
Message-ID: <4BFFE51B.3080504@codeaurora.org> (raw)
In-Reply-To: <20100528.004732.70206390.davem@davemloft.net>
David:
>
> Bluetooth patches should be sent to the linux-bluetooth@vger.kernel.org
> mailing list. As per the following linux/MAINTAINERS entries:
>
> BLUETOOTH DRIVERS
> M: Marcel Holtmann <marcel@holtmann.org>
> L: linux-bluetooth@vger.kernel.org
> W: http://www.bluez.org/
> S: Maintained
> F: drivers/bluetooth/
>
> BLUETOOTH SUBSYSTEM
> M: Marcel Holtmann <marcel@holtmann.org>
> L: linux-bluetooth@vger.kernel.org
> W: http://www.bluez.org/
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git
> S: Maintained
> F: net/bluetooth/
> F: include/net/bluetooth/
>
Yes. My apologizes. In a daze, I inappropriately gave the incorrect list for my To:
address.
Sorry for the inconvenience, and thanks for the reminder.
--
Ron Shaffer
Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
prev parent reply other threads:[~2010-05-28 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 3:12 [PATCH v3 0/3] Don't send SCO/eSCO request during a mode change from sniff to active Ron Shaffer
2010-05-28 3:12 ` [PATCH 1/3] Bluetooth: Remove extraneous white space Ron Shaffer
2010-05-28 3:26 ` [PATCH v3 0/3] Don't send SCO/eSCO request during a mode change from sniff to active Ron Shaffer
2010-05-28 3:12 ` [PATCH 2/3] Bluetooth: Reassigned copyright to Code Aurora Forum Ron Shaffer
2010-05-28 3:12 ` [PATCH 3/3] Bluetooth: Synchronize SCO/eSCO connection requests to ACL state Ron Shaffer
2010-05-28 7:47 ` [PATCH v3 0/3] Don't send SCO/eSCO request during a mode change from sniff to active David Miller
2010-05-28 15:45 ` Ron Shaffer [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=4BFFE51B.3080504@codeaurora.org \
--to=rshaffer@codeaurora.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@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).