linux-kernel - Re: [PATCH V1 2/2] i2c: tegra: support for I2C_M

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120510135411.3ba5bb6d@endymion.delvare>
Date:	Thu, 10 May 2012 13:54:11 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	w.sang@...gutronix.de, ben-linux@...ff.org, swarren@...dotorg.org,
	olof@...om.net, linux-i2c@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V1 2/2] i2c: tegra: support for I2C_M_NOSTART protocol 
 mangling

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
--
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/