From: Marcel Holtmann <marcel@holtmann.org>
To: "Mohanan, Rajmohan" <rajmohan.mohanan@intel.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"padovan@profusion.mobi" <padovan@profusion.mobi>
Subject: RE: LMP transaction collision at Set encryption
Date: Mon, 13 Feb 2012 11:41:10 +0100 [thread overview]
Message-ID: <1329129670.28848.64.camel@aeonflux> (raw)
In-Reply-To: <E74476E55D15D942BA0FF3CDAD73606F041FB8@FMSMSX102.amr.corp.intel.com>
Hi Rajmohan,
> I'm attaching Patch for LMP transaction collision.
> I could not Create patch according to Latest Bluez Tree because due to Project Constraints. Please review the patch . I have added Hcidump aslo.
please use git format-patch and then git send-email. If you have
problems with Exchange, then just point it to linux.intel.com and it
will work smoothly.
Reviewing attached patches is not something we do here. All patches need
to be inline.
Regards
Marcel
prev parent reply other threads:[~2012-02-13 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 6:22 LMP transaction collision at Set encryption Mohanan, Rajmohan
2012-02-13 7:28 ` Marcel Holtmann
2012-02-13 10:16 ` Mohanan, Rajmohan
2012-02-13 10:41 ` 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=1329129670.28848.64.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=rajmohan.mohanan@intel.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).