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]
Date: Sun, 16 Jun 2024 21:14:40 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Andi Shyti <andi.shyti@...nel.org>
Cc: linux-i2c@...r.kernel.org, 
	Easwar Hariharan <eahariha@...ux.microsoft.com>, linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 5/6] docs: i2c: summary: document 'local' and 'remote'
 targets

Hi Andi,

> I am not a big fan of the use of the word client. It's not used
> anywhere in the documentation and it's too generic as a name for
> giving it a specific meaning.
> 
> I've seen already some confusion amongst reviewers and
> maintainers when Easwar sent the patch in drm.
> 
> If it depends on me, I would stick to the only controller/target
> and render obsolet the use of the word "client" in the i2c
> context.

Have you read the paragraph "Synonyms" from patch 6? I don't think we
can obsolete client because:

$ git grep 'struct i2c_client \*client' | wc -l
6100

All the best,

   Wolfram


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ