From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759351Ab2EJLyk (ORCPT ); Thu, 10 May 2012 07:54:40 -0400 Received: from zoneX.GCU-Squad.org ([194.213.125.0]:33297 "EHLO services.gcu-squad.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757736Ab2EJLyi (ORCPT ); Thu, 10 May 2012 07:54:38 -0400 Date: Thu, 10 May 2012 13:54:11 +0200 From: Jean Delvare To: Laxman Dewangan Cc: w.sang@pengutronix.de, ben-linux@fluff.org, swarren@wwwdotorg.org, olof@lixom.net, linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH V1 2/2] i2c: tegra: support for I2C_M_NOSTART protocol mangling Message-ID: <20120510135411.3ba5bb6d@endymion.delvare> In-Reply-To: <4FABA585.7090600@nvidia.com> References: <1335251976-31925-1-git-send-email-ldewangan@nvidia.com> <1335251976-31925-3-git-send-email-ldewangan@nvidia.com> <4FABA585.7090600@nvidia.com> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.7; x86_64-suse-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Laxman, On Thu, 10 May 2012 16:54:53 +0530, Laxman Dewangan wrote: > Jean, > On Tuesday 24 April 2012 12:49 PM, Laxman Dewangan wrote: > > Adding support for protocol mangling I2C_M_NOSTART. > > When multiple message transfer request made through i2c > > and if any message is flagged with I2C_M_NOSTART then > > it will not send the start/repeat start/address of that > > message i.e. send the data directly. > > Now the framework/core changes for making M_NOSTART as a separate flag > is already part of your tree. > So do I need to re-send the patch for having that change? > 1/1 is already part of Wolfram's tree and so not sure that how do I go > i.e. from where I take the base i2c-tegra driver. > It may create the problem in integration on main if they are not sync. > Also I have some couple of changes which will be on top of this. I'm not sure I read you correctly so, for clarity: the patch introducing I2C_FUNC_NOSTART finally landed in my tree [1], not Wolfram's. It will be merged in kernel 3.5. [1] http://khali.linux-fr.org/devel/linux-3/jdelvare-i2c/ If you don't want to depend on that, then just use I2C_FUNC_PROTOCOL_MANGLING for now and you can switch to I2C_FUNC_NOSTART later. -- Jean Delvare