From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [CIFS] [PATCH] consistently use smb_buf_length as be32 for cifs (try 3) Date: Fri, 18 Mar 2011 14:51:54 -0400 Message-ID: <20110318185154.GA8028@infradead.org> References: <20110317164446.GA26600@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , linux-cifs@vger.kernel.org, linux-fsdevel To: Steve French Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:46792 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756267Ab1CRSvz (ORCPT ); Fri, 18 Mar 2011 14:51:55 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Mar 17, 2011 at 12:17:24PM -0500, Steve French wrote: > If others feel strongly about this, I don't mind changing it as > Christoph suggests but > - to samba people, "incrementing the rfc1001 length" would be more > recognizable (than opencoding the be32_add_cpu macro), and the > function name was > actually Jeff's suggestion which I liked. I don't mind the rfc1001 length per se. What's totally braindead about this is having an absolutely trivial wrapper for incrementing a field, which has a different name than the field it increments. If you feel strongly about the rfc1001 length just rename the field.