linux-kernel - Re: [PATCH 2/2] i2c: move locking operations to their own struct

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: <4ff4bdab-a322-8cf2-aec8-bfd4ae4c2f34@axentia.se>
Date:   Wed, 24 Aug 2016 09:47:19 +0200
From:   Peter Rosin <peda@...ntia.se>
To:     Wolfram Sang <wsa@...-dreams.de>
CC:     <linux-kernel@...r.kernel.org>, <linux-i2c@...r.kernel.org>
Subject: Re: [PATCH 2/2] i2c: move locking operations to their own struct

On 2016-08-23 23:16, Wolfram Sang wrote:
> On Fri, Jul 29, 2016 at 10:17:57AM +0200, Peter Rosin wrote:
>> This makes it trivial to constify them, so do that.
>>
>> Signed-off-by: Peter Rosin <peda@...ntia.se>
> 
> Looks good. Could you rebase to i2c/for-next?

Right, no problem!

Cheers,
Peter

The following changes since commit 00f0ea70d2b82b7d7afeb1bdedc9169eb8ea6675:

  eeprom: at24: check if the chip is functional in probe() (2016-08-22 08:19:58 +0200)

are available in the git repository at:

  https://github.com/peda-r/i2c-mux.git i2c-lock-op

for you to fetch changes up to 4b42b8c2e3233671e49deee71458edb6737a38bf:

  i2c: move locking operations to their own struct (2016-08-24 06:38:58 +0200)

----------------------------------------------------------------
Peter Rosin (2):
      i2c: add i2c_trylock_bus wrapper, use it
      i2c: move locking operations to their own struct

 drivers/i2c/i2c-core.c | 15 +++++++++------
 drivers/i2c/i2c-mux.c  | 29 ++++++++++++++++++-----------
 include/linux/i2c.h    | 37 +++++++++++++++++++++++++++++++------
 3 files changed, 58 insertions(+), 23 deletions(-)