From: patchwork-bot+linux-riscv@kernel.org
To: Conor Dooley <conor@kernel.org>
Cc: linux-riscv@lists.infradead.org, linux-i2c@vger.kernel.org,
conor.dooley@microchip.com, daire.mcnamara@microchip.com,
andi.shyti@kernel.org, wsa@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Microchip CoreI2C driver fixes
Date: Mon, 03 Feb 2025 19:16:00 +0000 [thread overview]
Message-ID: <173861016099.3409359.8425752210633125446.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241218-steadier-corridor-0c0a0ce58ca2@spud>
Hello:
This series was applied to riscv/linux.git (fixes)
by Andi Shyti <andi.shyti@kernel.org>:
On Wed, 18 Dec 2024 12:07:39 +0000 you wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Yo,
>
> Here's a v2 with one of the minor items pointed out by Andi resolved and
> a new patch for an issue fixed in the months since v1, plus some minor
> checkpatch things that I seem to have missed on v1. On v1 there was
> unresolved discussion with Wolfram, but it has been two months without a
> response so I am sending this v2 in an attempt to make progress.
>
> [...]
Here is the summary with links:
- [v2,1/2] i2c: microchip-core: actually use repeated sends
https://git.kernel.org/riscv/c/9a8f9320d67b
- [v2,2/2] i2c: microchip-core: fix "ghost" detections
https://git.kernel.org/riscv/c/49e1f0fd0d4c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-03 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 12:07 [PATCH v2 0/2] Microchip CoreI2C driver fixes Conor Dooley
2024-12-18 12:07 ` [PATCH v2 1/2] i2c: microchip-core: actually use repeated sends Conor Dooley
2024-12-18 12:07 ` [PATCH v2 2/2] i2c: microchip-core: fix "ghost" detections Conor Dooley
2024-12-19 11:50 ` [PATCH v2 0/2] Microchip CoreI2C driver fixes Andi Shyti
2024-12-26 0:59 ` Andi Shyti
2025-02-03 19:16 ` patchwork-bot+linux-riscv [this message]
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=173861016099.3409359.8425752210633125446.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=daire.mcnamara@microchip.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=wsa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox