public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "w.sang@pengutronix.de" <w.sang@pengutronix.de>,
	"ben-linux@fluff.org" <ben-linux@fluff.org>,
	"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
	"olof@lixom.net" <olof@lixom.net>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V1 2/2] i2c: tegra: support for I2C_M_NOSTART protocol mangling
Date: Thu, 10 May 2012 16:54:53 +0530	[thread overview]
Message-ID: <4FABA585.7090600@nvidia.com> (raw)
In-Reply-To: <1335251976-31925-3-git-send-email-ldewangan@nvidia.com>

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.

Thanks,
Laxman

  parent reply	other threads:[~2012-05-10 11:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24  7:19 [PATCH V1 0/2] i2c: tegra: 10 bit and M_NOSTART support Laxman Dewangan
2012-04-24  7:19 ` [PATCH V1 1/2] i2c: tegra: fix 10bit address configuration Laxman Dewangan
2012-04-24  8:58   ` Jean Delvare
2012-05-03  6:13     ` Laxman Dewangan
2012-05-03  8:18       ` Wolfram Sang
2012-05-03  8:20         ` Laxman Dewangan
2012-04-24  7:19 ` [PATCH V1 2/2] i2c: tegra: support for I2C_M_NOSTART protocol mangling Laxman Dewangan
2012-04-24  8:55   ` Jean Delvare
2012-04-24  9:21     ` Laxman Dewangan
2012-04-24 11:38       ` Mark Brown
2012-04-24 12:32       ` Jean Delvare
2012-04-24 12:40         ` Mark Brown
2012-04-24 13:01           ` Wolfram Sang
2012-04-24 13:07             ` Jean Delvare
2012-04-24 13:28               ` Wolfram Sang
2012-05-10 11:24   ` Laxman Dewangan [this message]
2012-05-10 11:54     ` Jean Delvare
2012-05-10 12:20       ` Laxman Dewangan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FABA585.7090600@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=ben-linux@fluff.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=swarren@wwwdotorg.org \
    --cc=w.sang@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox