netdev - Re: [PATCH v1 10/12] sfc: falcon: Make I2C terminology more inclusive

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: <20240503151300.0f202c30@kernel.org>
Date: Fri, 3 May 2024 15:13:00 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Easwar Hariharan <eahariha@...ux.microsoft.com>
Cc: Edward Cree <ecree.xilinx@...il.com>, Martin Habets
 <habetsm.xilinx@...il.com>, "David S. Miller" <davem@...emloft.net>, Eric
 Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Simon
 Horman <horms@...nel.org>, netdev@...r.kernel.org (open list:SFC NETWORK
 DRIVER), linux-net-drivers@....com (open list:SFC NETWORK DRIVER),
 linux-kernel@...r.kernel.org (open list), Wolfram Sang
 <wsa+renesas@...g-engineering.com>, amd-gfx@...ts.freedesktop.org (open
 list:RADEON and AMDGPU DRM DRIVERS), dri-devel@...ts.freedesktop.org (open
 list:DRM DRIVERS), intel-gfx@...ts.freedesktop.org (open list:INTEL DRM
 DISPLAY FOR XE AND I915 DRIVERS), intel-xe@...ts.freedesktop.org (open
 list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS),
 nouveau@...ts.freedesktop.org (open list:DRM DRIVER FOR NVIDIA
 GEFORCE/QUADRO GPUS), linux-i2c@...r.kernel.org (open list:I2C SUBSYSTEM
 HOST DRIVERS), linux-media@...r.kernel.org (open list:BTTV VIDEO4LINUX
 DRIVER), linux-fbdev@...r.kernel.org (open list:FRAMEBUFFER LAYER)
Subject: Re: [PATCH v1 10/12] sfc: falcon: Make I2C terminology more
 inclusive

On Tue, 30 Apr 2024 17:38:09 +0000 Easwar Hariharan wrote:
> I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
> with more appropriate terms. Inspired by and following on to Wolfram's
> series to fix drivers/i2c/[1], fix the terminology for users of
> I2C_ALGOBIT bitbanging interface, now that the approved verbiage exists
> in the specification.
> 
> Compile tested, no functionality changes intended

FWIW we're assuming someone (Wolfram?) will take all of these,
instead of area maintainers picking them individually.
Please let us know if that's incorrect.