From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754221AbZHRPnV (ORCPT ); Tue, 18 Aug 2009 11:43:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759241AbZHRPnU (ORCPT ); Tue, 18 Aug 2009 11:43:20 -0400 Received: from mail.cs.nmsu.edu ([128.123.64.3]:36584 "EHLO mail.cs.nmsu.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751002AbZHRPnU (ORCPT ); Tue, 18 Aug 2009 11:43:20 -0400 Message-ID: In-Reply-To: References: Date: Tue, 18 Aug 2009 09:43:14 -0600 Subject: Re: Purpose of parameter in sysfs binary read From: "Rick L. Vinyard, Jr." To: "Alan Stern" Cc: "Linux USB" , "LKML" User-Agent: SquirrelMail/1.4.19 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Alan Stern wrote: > On Tue, 18 Aug 2009, Rick L. Vinyard, Jr. wrote: > > Neither one. If the kernel wanted to add an offset to buf, it would > have done so before calling the function. The code should be more like > this: > > memcpy(buf, bindata + offset, min(size, bsize - offset)); > Ahhh, offset into the binary data. Thanks.