lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 20 Aug 2012 11:36:16 -0600 From: Stephen Warren <swarren@...dotorg.org> To: Laxman Dewangan <ldewangan@...dia.com> CC: "khali@...ux-fr.org" <khali@...ux-fr.org>, "w.sang@...gutronix.de" <w.sang@...gutronix.de>, Stephen Warren <swarren@...dia.com>, "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org> Subject: Re: [PATCH V2 1/2] i2c: tegra: I2_M_NOSTART functionality not supported in Tegra20 On 08/20/2012 11:10 AM, Laxman Dewangan wrote: > 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.. Ah. This is something new in linux-next but not in 3.6-rc2. It was introduced by: 98d7bbb of: add const to struct *of_device_id.data I'll revert the modifications I made to the patch, and ignore the warnings in Tegra's for-next; they won't be present in 3.7 presumably. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists