From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Andi Shyti" <andi.shyti@linux.intel.com>,
"Wolfram Sang" <wsa@kernel.org>,
"open list:RADEON and AMDGPU DRM DRIVERS"
<amd-gfx@lists.freedesktop.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list" <linux-kernel@vger.kernel.org>
Cc: eahariha@linux.microsoft.com,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
"open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS"
<intel-gfx@lists.freedesktop.org>,
Wenjing Liu <wenjing.liu@amd.com>,
"open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS"
<intel-xe@lists.freedesktop.org>, Samson Tam <samson.tam@amd.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"open list:I2C SUBSYSTEM HOST DRIVERS"
<linux-i2c@vger.kernel.org>, Charlene Liu <charlene.liu@amd.com>,
Leo Li <sunpeng.li@amd.com>, Bob Zhou <bob.zhou@amd.com>,
Harry Wentland <harry.wentland@amd.com>,
"open list:FRAMEBUFFER LAYER" <linux-fbdev@vger.kernel.org>,
Sohaib Nadeem <sohaib.nadeem@amd.com>,
Yifan Zhang <yifan1.zhang@amd.com>, Le Ma <le.ma@amd.com>,
Aric Cyr <aric.cyr@amd.com>,
Aurabindo Pillai <aurabindo.pillai@amd.com>,
Li Ma <li.ma@amd.com>, Ran Sun <sunran001@208suo.com>,
Evan Quan <evan.quan@amd.com>, Candice Li <candice.li@amd.com>,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
Dillon Varone <dillon.varone@amd.com>,
Ruan Jinjie <ruanjinjie@huawei.com>,
Hamza Mahfooz <hamza.mahfooz@amd.com>,
Umio Yasuno <coelacanth_dream@protonmail.com>,
Alvin Lee <alvin.lee2@amd.com>, Ma Jun <Jun.Ma2@amd.com>,
Lijo Lazar <lijo.lazar@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Darren Powell <darren.powell@amd.com>,
Qingqing Zhuo <Qingqing.Zhuo@amd.com>,
Tom Chung <chiahsuan.chung@amd.com>,
Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>,
Meenakshikumar Somasundaram <meenakshikumar.somasundaram@amd.com>,
George Shen <george.shen@amd.com>,
Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
Alex Hung <alex.hung@amd.com>, Wayne Lin <wayne.lin@amd.com>,
Hawking Zhang <Hawking.Zhang@amd.com>,
Likun Gao <Likun.Gao@amd.com>,
Alexander Richards <electrodeyt@gmail.com>
Subject: Re: [PATCH v4 1/6] drm/amdgpu, drm/radeon: Make I2C terminology more inclusive
Date: Mon, 29 Jul 2024 19:03:28 -0700 [thread overview]
Message-ID: <c8023385-8fb8-432c-acf6-10e9a2894e2a@linux.microsoft.com> (raw)
In-Reply-To: <20240711052734.1273652-2-eahariha@linux.microsoft.com>
On 7/10/2024 10:27 PM, Easwar Hariharan wrote:
> I2C v7, SMBus 3.2, and I3C 1.1.1 specifications have replaced "master/slave"
> with more appropriate terms. Inspired by Wolfram's series to fix drivers/i2c/,
> fix the terminology for users of I2C_ALGOBIT bitbanging interface, now that
> the approved verbiage exists in the specification.
>
> Acked-by: Alex Deucher <alexander.deucher@amd.com>
> Signed-off-by: Easwar Hariharan <eahariha@linux.microsoft.com>
> ---
> .../gpu/drm/amd/amdgpu/amdgpu_atomfirmware.c | 8 +++---
> drivers/gpu/drm/amd/amdgpu/amdgpu_i2c.c | 10 +++----
> drivers/gpu/drm/amd/amdgpu/atombios_i2c.c | 8 +++---
> drivers/gpu/drm/amd/amdgpu/atombios_i2c.h | 2 +-
> drivers/gpu/drm/amd/amdgpu/smu_v11_0_i2c.c | 20 ++++++-------
> .../gpu/drm/amd/display/dc/bios/bios_parser.c | 2 +-
> .../drm/amd/display/dc/bios/bios_parser2.c | 2 +-
> .../drm/amd/display/dc/core/dc_link_exports.c | 4 +--
> drivers/gpu/drm/amd/display/dc/dc.h | 2 +-
> drivers/gpu/drm/amd/display/dc/dce/dce_i2c.c | 4 +--
> .../display/include/grph_object_ctrl_defs.h | 2 +-
> drivers/gpu/drm/amd/include/atombios.h | 2 +-
> drivers/gpu/drm/amd/include/atomfirmware.h | 26 ++++++++---------
> .../powerplay/hwmgr/vega20_processpptables.c | 4 +--
> .../amd/pm/powerplay/inc/smu11_driver_if.h | 2 +-
> .../inc/pmfw_if/smu11_driver_if_arcturus.h | 2 +-
> .../inc/pmfw_if/smu11_driver_if_navi10.h | 2 +-
> .../pmfw_if/smu11_driver_if_sienna_cichlid.h | 2 +-
> .../inc/pmfw_if/smu13_driver_if_aldebaran.h | 2 +-
> .../inc/pmfw_if/smu13_driver_if_v13_0_0.h | 2 +-
> .../inc/pmfw_if/smu13_driver_if_v13_0_7.h | 2 +-
> .../gpu/drm/amd/pm/swsmu/smu11/arcturus_ppt.c | 4 +--
> .../amd/pm/swsmu/smu11/sienna_cichlid_ppt.c | 8 +++---
> drivers/gpu/drm/radeon/atombios.h | 16 +++++------
> drivers/gpu/drm/radeon/atombios_i2c.c | 4 +--
> drivers/gpu/drm/radeon/radeon_combios.c | 28 +++++++++----------
> drivers/gpu/drm/radeon/radeon_i2c.c | 10 +++----
> drivers/gpu/drm/radeon/radeon_mode.h | 6 ++--
> 28 files changed, 93 insertions(+), 93 deletions(-)
>
Hi Alex, Christian, Xinhui, David, Daniel, others
This is the only patch in the series not merged into a tree. Is
something needed from me to move this forward?
Thanks,
Easwar
next prev parent reply other threads:[~2024-07-30 2:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 5:27 [PATCH v4 0/6] Make I2C terminology more inclusive for I2C Algobit and consumers Easwar Hariharan
2024-07-11 5:27 ` [PATCH v4 1/6] drm/amdgpu, drm/radeon: Make I2C terminology more inclusive Easwar Hariharan
2024-07-30 2:03 ` Easwar Hariharan [this message]
2024-07-11 5:27 ` [PATCH v4 2/6] drm/gma500: " Easwar Hariharan
2024-07-29 7:41 ` Thomas Zimmermann
2024-07-11 5:27 ` [PATCH v4 3/6] drm/i915: " Easwar Hariharan
2024-07-11 11:24 ` Andi Shyti
2024-07-18 9:54 ` Andi Shyti
2024-07-22 12:50 ` Andi Shyti
2024-07-22 16:15 ` Easwar Hariharan
2024-07-22 16:27 ` Andi Shyti
2024-07-11 5:27 ` [PATCH v4 4/6] sfc: falcon: " Easwar Hariharan
2024-07-14 0:00 ` patchwork-bot+netdevbpf
2024-07-11 5:27 ` [PATCH v4 5/6] fbdev/smscufx: " Easwar Hariharan
2024-07-11 10:08 ` Helge Deller
2024-07-11 5:27 ` [PATCH v4 6/6] fbdev/viafb: " Easwar Hariharan
2024-07-11 10:09 ` Helge Deller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c8023385-8fb8-432c-acf6-10e9a2894e2a@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Hawking.Zhang@amd.com \
--cc=Jun.Ma2@amd.com \
--cc=Likun.Gao@amd.com \
--cc=Qingqing.Zhuo@amd.com \
--cc=Rodrigo.Siqueira@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alvin.lee2@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andi.shyti@linux.intel.com \
--cc=aric.cyr@amd.com \
--cc=aurabindo.pillai@amd.com \
--cc=bob.zhou@amd.com \
--cc=candice.li@amd.com \
--cc=charlene.liu@amd.com \
--cc=chiahsuan.chung@amd.com \
--cc=christian.koenig@amd.com \
--cc=coelacanth_dream@protonmail.com \
--cc=daniel@ffwll.ch \
--cc=darren.powell@amd.com \
--cc=dillon.varone@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=electrodeyt@gmail.com \
--cc=evan.quan@amd.com \
--cc=george.shen@amd.com \
--cc=hamza.mahfooz@amd.com \
--cc=harry.wentland@amd.com \
--cc=hkallweit1@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=le.ma@amd.com \
--cc=li.ma@amd.com \
--cc=lijo.lazar@amd.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=meenakshikumar.somasundaram@amd.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=ruanjinjie@huawei.com \
--cc=samson.tam@amd.com \
--cc=sohaib.nadeem@amd.com \
--cc=sunpeng.li@amd.com \
--cc=sunran001@208suo.com \
--cc=wayne.lin@amd.com \
--cc=wenjing.liu@amd.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@kernel.org \
--cc=yifan1.zhang@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox