linux-kernel - Re: [PATCH 22/64] i2c: highlander: reword according to newest specification

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: <45c4rorg4lgntiunjecqxwlr5hz4e7qrxr2q3xzzh5kv7ebpwx@6hn6p2ttfes7>
Date: Wed, 10 Apr 2024 17:19:59 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>, 
	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Easwar Hariharan <eahariha@...ux.microsoft.com>
Subject: Re: [PATCH 22/64] i2c: highlander: reword according to newest
 specification

Hi Wolfram,

On Mon, Apr 08, 2024 at 11:07:20AM +0200, Wolfram Sang wrote:
> > I'm just noticing... what do you mean with client/target? Can you
> > please be a bit more specific?
> 
> I described it somewhere (and Easwar mentioned it in another thread by
> now), but, yes, it needs to be better described. This will be also in my
> updates to the I2C docs.

yes, I understood the difference between "client" and "target".
The problem I see here is that this is not described in the
specification (except for some pictures in the i3c, iirc).

So that the change slave/client looks a bit arbitrary and I hear
some people don't like it.

That's why I need to know a bit more about the choice :-)

Thanks,
Andi