From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: "khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org"
<khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
"w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org"
<w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V2 1/2] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20
Date: Mon, 20 Aug 2012 22:40:26 +0530 [thread overview]
Message-ID: <50326F82.3050503@nvidia.com> (raw)
In-Reply-To: <503270B3.7000007-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On Monday 20 August 2012 10:45 PM, Stephen Warren wrote:
> 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.
Thanks for correction but
I did not get this warning and when saw the structure, it is declared as
const type only..
struct of_device_id
{
char name[32];
char type[32];
char compatible[128];
#ifdef __KERNEL__
const void *data;
#else
kernel_ulong_t data;
#endif
};
WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "khali@linux-fr.org" <khali@linux-fr.org>,
"w.sang@pengutronix.de" <w.sang@pengutronix.de>,
Stephen Warren <swarren@nvidia.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@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 22:40:26 +0530 [thread overview]
Message-ID: <50326F82.3050503@nvidia.com> (raw)
In-Reply-To: <503270B3.7000007@wwwdotorg.org>
On Monday 20 August 2012 10:45 PM, Stephen Warren wrote:
> 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.
Thanks for correction but
I did not get this warning and when saw the structure, it is declared as
const type only..
struct of_device_id
{
char name[32];
char type[32];
char compatible[128];
#ifdef __KERNEL__
const void *data;
#else
kernel_ulong_t data;
#endif
};
next prev parent reply other threads:[~2012-08-20 17:10 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
[not found] ` <503270B3.7000007-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-20 17:10 ` Laxman Dewangan [this message]
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=50326F82.3050503@nvidia.com \
--to=ldewangan-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
/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.