From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <1329118089.28848.60.camel@aeonflux> Subject: RE: LMP transaction collision at Set encryption From: Marcel Holtmann To: "Mohanan, Rajmohan" Cc: "linux-bluetooth@vger.kernel.org" , "padovan@profusion.mobi" Date: Mon, 13 Feb 2012 08:28:09 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Rajmohan, > 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