This is a resend of last nights patch's to address Gustavo's confusion over the Patch Revision. I have relabeled these as Patch version "3" to account for them being the third set, although I had not ever correctly labeled anything as Patch revision "2". The rest of Gustavo's comments were essentially the same as Marcel's, which were to address sparseness and in some cases lack of commit messages. Re-Including the the other cover page info below: This patch set is nearly identical to the previous patchset, except that I added MGMT_EV_USER_PASSKEY_REQUEST, and related functions to make more fully symmetric with MGMT_EV_USER_CONFIRM_REQUEST. Otherwise, more of the same, and the rest of my original connects apply: This patch set addresses all the issues that I saw raised. The first two are the header only changes previously Acked by Marcel. The main MGMT changes are in patch 3 and 4. Patch 3 restructures the User Pairing input without adding any functionality. Patch 4 adds in the Passkey entry, in the style introduced in 3, reusing the shared common code. Patch 5 handles the Passkey Request event, and the Cmd Cmplt events generated by the Passkey Response commands. Patches 6 and 7 clean-up some issues in SMP that could leak memory, and complete notification to User space of pairing failures. In patch 8, we have the actual addition of the MITM changes for SMP, with calls into MGMT to obtain Passkeys and/or Confirmations. Patch 9 adds the calls back into SMP with Passkey/Confirmation results. -- Brian Gix bgix@xxxxxxxxxxxxxx Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum -- 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
