Return-path: Received: from mail-ob0-f178.google.com ([209.85.214.178]:47534 "EHLO mail-ob0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751408AbaK2SyU (ORCPT ); Sat, 29 Nov 2014 13:54:20 -0500 Message-ID: <547A1659.9070605@lwfinger.net> (sfid-20141129_195505_739862_B6A9137E) Date: Sat, 29 Nov 2014 12:54:17 -0600 From: Larry Finger MIME-Version: 1.0 To: nick , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , =?UTF-8?B?TWljaGFlbCBCw7xzY2g=?= CC: Network Development , "linux-wireless@vger.kernel.org" , Linux Kernel Mailing List , Stefano Brivio , b43-dev Subject: Re: [PATCH] drivers:net:wireless: Add mutex locking for function, b43_op_beacon_set_time in main.c References: <1417213013-19758-1-git-send-email-xerofoify@gmail.com> <20141129002148.1beb21d9@wiggum> <54793E4E.7050602@gmail.com> <20141129095632.69361457@wiggum> <547A0BC5.2080005@gmail.com> In-Reply-To: <547A0BC5.2080005@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 11/29/2014 12:09 PM, nick wrote: > Sorry about that, next time I will be more careful. One other thing would be to change the initial part of the subject. Yes, the device is in drivers/net/wireless/, but it is much more common to not include those in patches that are sent to Linville. I would have used "b43: Add ...". That catches the eye more quickly. As they say in the newspaper business, "Don't bury the lead." Larry