From: Easwar Hariharan <eahariha@linux.microsoft.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: eahariha@linux.microsoft.com,
Jani Nikula <jani.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Tvrtko Ursulin <tursulin@ursulin.net>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Zhenyu Wang <zhenyuw@linux.intel.com>,
Zhi Wang <zhi.wang.linux@gmail.com>,
"open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS"
<intel-gfx@lists.freedesktop.org>,
"open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS"
<intel-xe@lists.freedesktop.org>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:INTEL GVT-g DRIVERS (Intel GPU Virtualization)"
<intel-gvt-dev@lists.freedesktop.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
"open list:RADEON and AMDGPU DRM DRIVERS"
<amd-gfx@lists.freedesktop.org>,
"open list:I2C SUBSYSTEM HOST DRIVERS"
<linux-i2c@vger.kernel.org>,
"open list:FRAMEBUFFER LAYER" <linux-fbdev@vger.kernel.org>,
Zhi Wang <zhiwang@kernel.org>
Subject: Re: [PATCH v4 3/6] drm/i915: Make I2C terminology more inclusive
Date: Mon, 22 Jul 2024 09:15:08 -0700 [thread overview]
Message-ID: <24fa9e9b-81a8-4bbe-8d13-4d559ee76a96@linux.microsoft.com> (raw)
In-Reply-To: <Zp5Vq9JoYC_OrA2C@ashyti-mobl2.lan>
On 7/22/2024 5:50 AM, Andi Shyti wrote:
> Hi Easwar,
>
> merged to drm-intel-next. Thanks!
>
> On Thu, Jul 11, 2024 at 05:27:31AM +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 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.
>>
>> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> I realized after pushing that this had the tag:
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Not a big deal, but it's still a minor mistake.
>
> Andi
Thank you for the merge, Andi! I'm missing what the mistake is, I added
the tags as I got them. Was I supposed to drop the R-B when Rodrigo gave
an A-B?
Thanks,
Easwar
next prev parent reply other threads:[~2024-07-23 13:02 UTC|newest]
Thread overview: 34+ 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
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 [this message]
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
2024-07-11 5:58 ` ✓ CI.Patch_applied: success for Make I2C terminology more inclusive for I2C Algobit and consumers (rev5) Patchwork
2024-07-11 5:58 ` ✗ CI.checkpatch: warning " Patchwork
2024-07-11 6:00 ` ✓ CI.KUnit: success " Patchwork
2024-07-11 6:11 ` ✓ CI.Build: " Patchwork
2024-07-11 6:14 ` ✓ CI.Hooks: " Patchwork
2024-07-11 6:15 ` ✗ CI.checksparse: warning " Patchwork
2024-07-11 6:46 ` ✗ CI.BAT: failure " Patchwork
2024-07-11 7:04 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-07-11 7:04 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-07-11 7:13 ` ✓ Fi.CI.BAT: success " Patchwork
2024-07-11 7:54 ` ✗ CI.FULL: failure " Patchwork
2024-07-11 17:59 ` Easwar Hariharan
2024-07-11 11:54 ` ✗ Fi.CI.IGT: " Patchwork
2024-07-18 10:45 ` ✗ Fi.CI.CHECKPATCH: warning for Make I2C terminology more inclusive for I2C Algobit and consumers (rev7) Patchwork
2024-07-18 10:45 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-07-18 10:53 ` ✓ Fi.CI.BAT: success " Patchwork
2024-07-19 6:18 ` ✓ Fi.CI.IGT: " Patchwork
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=24fa9e9b-81a8-4bbe-8d13-4d559ee76a96@linux.microsoft.com \
--to=eahariha@linux.microsoft.com \
--cc=airlied@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andi.shyti@linux.intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tursulin@ursulin.net \
--cc=wsa+renesas@sang-engineering.com \
--cc=zhenyuw@linux.intel.com \
--cc=zhi.wang.linux@gmail.com \
--cc=zhiwang@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.