From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Dan Tian <Dan.Tian@Atheros.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Haijun Liu <Haijun.Liu@Atheros.com>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH 3/3] Add eL2cap implementation, by Atheros Linux BT3 team.
Date: Thu, 15 Jul 2010 11:51:05 -0700 [thread overview]
Message-ID: <20100715185105.GG1166@tux> (raw)
In-Reply-To: <CDAFEDABF718A54BABD0DA5476695307CE881F90@SHEXMB-01.global.atheros.com>
On Thu, Jul 15, 2010 at 04:59:45AM -0700, Dan Tian wrote:
> The third patch, which is too big to send via pure text in email.
>
> Please see attached.
I'm not sure if MIME attachments are accepted to linux-bluetooth so
I've scp'd the patch you attached and that I did get to kernel.org
for others to wget:
http://kernel.org/pub/linux/kernel/people/mcgrof/patches/bluetooth/BT-3.0/
Luis
parent reply other threads:[~2010-07-15 18:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CDAFEDABF718A54BABD0DA5476695307CE881F90@SHEXMB-01.global.atheros.com>]
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=20100715185105.GG1166@tux \
--to=lrodriguez@atheros.com \
--cc=Dan.Tian@Atheros.com \
--cc=Haijun.Liu@Atheros.com \
--cc=Luis.Rodriguez@Atheros.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 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).