All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: ecree.xilinx@gmail.com, habetsm.xilinx@gmail.com,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
	linux-net-drivers@amd.com, linux-kernel@vger.kernel.org,
	wsa+renesas@sang-engineering.com, andi.shyti@linux.intel.com,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
	linux-i2c@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v4 4/6] sfc: falcon: Make I2C terminology more inclusive
Date: Sun, 14 Jul 2024 00:00:30 +0000	[thread overview]
Message-ID: <172091523039.919.13223034713999192575.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240711052734.1273652-5-eahariha@linux.microsoft.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 11 Jul 2024 05:27:32 +0000 you 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: Martin Habets <habetsm.xilinx@gmail.com>
> Reviewed-by: Simon Horman <horms@kernel.org>
> Signed-off-by: Easwar Hariharan <eahariha@linux.microsoft.com>
> 
> [...]

Here is the summary with links:
  - [v4,4/6] sfc: falcon: Make I2C terminology more inclusive
    https://git.kernel.org/netdev/net-next/c/ba88b47816a2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2024-07-14  0:01 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
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 [this message]
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=172091523039.919.13223034713999192575.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=andi.shyti@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eahariha@linux.microsoft.com \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=habetsm.xilinx@gmail.com \
    --cc=horms@kernel.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=kuba@kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wsa+renesas@sang-engineering.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 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.