All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: khali@linux-fr.org, w.sang@pengutronix.de, swarren@nvidia.com,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2 1/2] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20
Date: Mon, 20 Aug 2012 11:15:31 -0600	[thread overview]
Message-ID: <503270B3.7000007@wwwdotorg.org> (raw)
In-Reply-To: <1345317467-22258-1-git-send-email-ldewangan@nvidia.com>

On 08/18/2012 01:17 PM, Laxman Dewangan wrote:
> Tegra20 i2c controller does not support the continue transfer
> which implements the I2C_M_NOSTART functionality of i2c
> protocol mangling.
> Removing the I2C_M_NOSTART functionality support for Tegra20.

Thanks, applied the series to Tegra's for-3.7/drivers-i2c branch.

Note that I had to fix up patch 1 to remove const on the tegra*_i2c_hw
variable declarations to avoid compiler warnings when assigning pointers
into tegra_i2c_of_match[].data.

  parent reply	other threads:[~2012-08-20 17:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18 19:17 [PATCH V2 1/2] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20 Laxman Dewangan
2012-08-18 19:17 ` Laxman Dewangan
     [not found] ` <1345317467-22258-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-18 19:17   ` [PATCH V2 2/2] i2c: tegra: dynamically control fast clk Laxman Dewangan
2012-08-18 19:17     ` Laxman Dewangan
2012-08-19  6:33 ` [PATCH V2 1/2] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20 Wolfram Sang
2012-08-20 17:15 ` Stephen Warren [this message]
     [not found]   ` <503270B3.7000007-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-20 17:10     ` Laxman Dewangan
2012-08-20 17:10       ` Laxman Dewangan
     [not found]       ` <50326F82.3050503-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-08-20 17:36         ` Stephen Warren
2012-08-20 17:36           ` Stephen Warren

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=503270B3.7000007@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=khali@linux-fr.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.