From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754152AbcFPQKz (ORCPT ); Thu, 16 Jun 2016 12:10:55 -0400 Received: from www381.your-server.de ([78.46.137.84]:41165 "EHLO www381.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751619AbcFPQKy (ORCPT ); Thu, 16 Jun 2016 12:10:54 -0400 Subject: Re: [PATCH] spi: add spi_sync_single_transfer wrapper for single spi_transfer To: Andi Shyti , Mark Brown References: <1466034046-718-1-git-send-email-andi.shyti@samsung.com> Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org, Andi Shyti From: Lars-Peter Clausen Message-ID: <5762CF88.4060800@metafoo.de> Date: Thu, 16 Jun 2016 18:10:48 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.8.0 MIME-Version: 1.0 In-Reply-To: <1466034046-718-1-git-send-email-andi.shyti@samsung.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Authenticated-Sender: lars@metafoo.de Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/16/2016 01:40 AM, Andi Shyti wrote: > The spi_sync_single_transfer function calls spi_sync_transfer > with a single spi_transfer element, instead of an array. So, what's the advantage of using this as opposed to calling spi_sync_transfer with a 1 for the number of transfers?