Hi Marcel,
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.
Regards
Rajmohan
-----Original Message-----
From: linux-bluetooth-owner@xxxxxxxxxxxxxxx [mailto:linux-bluetooth-owner@xxxxxxxxxxxxxxx] On Behalf Of Marcel Holtmann
Sent: Monday, February 13, 2012 12:58 PM
To: Mohanan, Rajmohan
Cc: linux-bluetooth@xxxxxxxxxxxxxxx; padovan@xxxxxxxxxxxxxx
Subject: RE: LMP transaction collision at Set encryption
Hi Rajmohan,
<snip>
> I'm attaching patch for above two issues.
>
> Please review it and let me know the feedback.
please send one patch per email. That is what git format-patch and git send-email are for.
The commit message needs to have a clear explanation of the issue and how you are fixing it. Including hcidump log is a good idea as well in these cases where you have some protocol issues.
Patches need to be signed-off-by and should not contain change-id (that is Android Gerrit stuff).
Also patches need to be against the latest bluetooth-next tree.
Userspace patches should not contain signed-off-by and also no change-id here as well.
The need to be against latest upstream and #if hacking is not allowed of course.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Attachment:
0001-LMP-transaction-collision-at-Set-encryption.patch
Description: 0001-LMP-transaction-collision-at-Set-encryption.patch
