From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i3c@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Jean Delvare" <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, "Przemysław Gaj" <pgaj@cadence.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Yury Norov" <yury.norov@gmail.com>
Subject: Re: [PATCH v4 0/5] i3c: introduce and use generic parity helper
Date: Wed, 8 Jan 2025 08:23:50 +0100 [thread overview]
Message-ID: <Z34oBoS0KL4Uz2Jn@shikoro> (raw)
In-Reply-To: <20250107090204.6593-1-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 98 bytes --]
> A build-tested branch is here:
That was locally built. Now, build bot said it is happy, too.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-08 7:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 9:01 [PATCH v4 0/5] i3c: introduce and use generic parity helper Wolfram Sang
2025-01-07 9:01 ` [PATCH v4 1/5] bitops: add generic parity calculation for u8 Wolfram Sang
2025-01-07 9:02 ` [PATCH v4 2/5] hwmon: (spd5118) Use generic parity calculation Wolfram Sang
2025-01-07 9:02 ` [PATCH v4 3/5] i3c: dw: use parity8 helper instead of open coding it Wolfram Sang
2025-01-07 9:02 ` [PATCH v4 4/5] i3c: mipi-i3c-hci: " Wolfram Sang
2025-01-08 12:09 ` Jarkko Nikula
2025-01-08 12:56 ` Wolfram Sang
2025-01-08 15:32 ` Jarkko Nikula
2025-01-07 9:02 ` [PATCH v4 5/5] i3c: cdns: " Wolfram Sang
2025-01-08 7:23 ` Wolfram Sang [this message]
2025-01-12 23:05 ` [PATCH v4 0/5] i3c: introduce and use generic parity helper Alexandre Belloni
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=Z34oBoS0KL4Uz2Jn@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=pgaj@cadence.com \
--cc=yury.norov@gmail.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