Re: [PATCH v0 01/14] IB/hfi1, IB/qib: Make I2C terminology more inclusive

2024-04-03 Thread Dennis Dalessandro
On 4/3/24 4:30 AM, Leon Romanovsky wrote: > On Fri, Mar 29, 2024 at 05:00:25PM +, Easwar Hariharan wrote: >> I2C v7, SMBus 3.2, and I3C specifications have replaced "master/slave" >> with more appropriate terms. Inspired by and following on to Wolfram's series >> to fix drivers/i2c[1], fix th

Re: [PATCH v0 01/14] IB/hfi1, IB/qib: Make I2C terminology more inclusive

2024-04-03 Thread Easwar Hariharan
On 4/3/2024 8:54 AM, Dennis Dalessandro wrote: > > On 4/3/24 4:30 AM, Leon Romanovsky wrote: >> On Fri, Mar 29, 2024 at 05:00:25PM +, Easwar Hariharan wrote: >>> I2C v7, SMBus 3.2, and I3C specifications have replaced "master/slave" >>> with more appropriate terms. Inspired by and following on

Re: [PATCH v0 01/14] IB/hfi1, IB/qib: Make I2C terminology more inclusive

2024-04-03 Thread Leon Romanovsky
On Fri, Mar 29, 2024 at 05:00:25PM +, Easwar Hariharan wrote: > I2C v7, SMBus 3.2, and I3C 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 where I had a role to play, now >

[PATCH v0 01/14] IB/hfi1, IB/qib: Make I2C terminology more inclusive

2024-03-29 Thread Easwar Hariharan
I2C v7, SMBus 3.2, and I3C 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 where I had a role to play, now that the approved verbiage exists in the specification. Compile tested, no