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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 5 Nov 2009 15:07:15 +0100 From: Jean Delvare <khali@...ux-fr.org> To: Ben Hutchings <bhutchings@...arflare.com> Cc: Stephen Rothwell <sfr@...b.auug.org.au>, David Miller <davem@...emloft.net>, netdev@...r.kernel.org, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org, Mika Kuoppala <mika.kuoppala@...ia.com>, Linux I2C <linux-i2c@...r.kernel.org> Subject: Re: Shared i2c adapter locking On Thu, 05 Nov 2009 13:57:24 +0000, Ben Hutchings wrote: > On Thu, 2009-11-05 at 14:11 +0100, Jean Delvare wrote: > [...] > > What about the following patch? > > > > From: Jean Delvare <khali@...ux-fr.org> > > Subject: i2c: Add an interface to lock/unlock I2C bus segment > > > > Some drivers need to be able to prevent access to an I2C bus segment > > for a specific period of time. Add an interface for them to do so > > without twiddling with i2c-core internals. > > > > Signed-off-by: Jean Delvare <khali@...ux-fr.org> > > Cc: Ben Hutchings <bhutchings@...arflare.com> > Acked-by: Ben Hutchings <bhutchings@...arflare.com> > > Presumably this is meant for net-next-2.6, and you'll implement Actually I meant to push this to Linus immediately, through my i2c tree. This is essentially a no-op: the binary code will be the same as before the patch, so guaranteed to be safe, and this will solve conflicts in linux-next. > i2c_{lock,unlock}_adapter() using rt_mutex in your i2c tree? Correct. -- 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/
Powered by blists - more mailing lists