Return-Path: MIME-Version: 1.0 In-Reply-To: References: <1338453008-15947-1-git-send-email-frederic.dalleau@linux.intel.com> <1338453008-15947-2-git-send-email-frederic.dalleau@linux.intel.com> Date: Thu, 31 May 2012 16:09:31 +0300 Message-ID: Subject: Re: [PATCH] network: Reply to extensions at connection setup From: Luiz Augusto von Dentz To: "Dalleau, Frederic" Cc: =?ISO-8859-1?Q?Fr=E9d=E9ric_Dalleau?= , linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Frederic, On Thu, May 31, 2012 at 3:09 PM, Dalleau, Frederic wrote: > Luiz, > > On Thu, May 31, 2012 at 12:38 PM, Luiz Augusto von Dentz > wrote: >> Hi Fr?d?ric, >> Perhaps you can have a macro for getting just the header type without >> the extension bit e.g. BNEP_HEADER(type) ((type) & ~BNEP_EXT_HEADER) >> > > Why not, but in this case, it would make sense to also define a macro > for reading the extension bit > Something like : #define BNEP_EXTENDED(type) ((type) & BNEP_EXT_HEADER) Yep, anything that makes it more obvious what it is doing is a good idea to have. -- Luiz Augusto von Dentz