From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Yury Norov <yury.norov@gmail.com>,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hwmon@vger.kernel.org,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: Re: [RFC PATCH 1/2] bitops: add generic parity calculation for u8
Date: Tue, 17 Dec 2024 09:41:03 +0100 [thread overview]
Message-ID: <Z2E5H3-vNIi2_6oT@shikoro> (raw)
In-Reply-To: <Z2ESttIzF4kX7JA-@shikoro>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
> I hope that both patches can be applied in one go to avoid a dependency.
> I'd think the hwmon-tree is a tad more suitable, but I am also fine with
> bitmap as long as both patches go in. What do you maintainers thing?
Second thought, we can ask I3C to take it. Together with the cleanups
for the I3C drivers I would add then.
If this is not to your likings, then an immutable branch for I3C to pull
in would be helpful, though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-17 8:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 8:58 [RFC PATCH 0/2] add generic parity calculation for u8 Wolfram Sang
2024-12-14 8:58 ` [RFC PATCH 1/2] bitops: " Wolfram Sang
2024-12-14 14:19 ` Guenter Roeck
2024-12-14 14:30 ` Guenter Roeck
2024-12-14 16:40 ` Wolfram Sang
2024-12-14 15:10 ` Guenter Roeck
2024-12-16 9:49 ` Geert Uytterhoeven
2024-12-17 2:24 ` Yury Norov
2024-12-17 5:57 ` Wolfram Sang
2024-12-17 8:41 ` Wolfram Sang [this message]
2024-12-17 13:10 ` Guenter Roeck
2024-12-17 8:15 ` Kuan-Wei Chiu
2024-12-17 8:37 ` Wolfram Sang
2024-12-14 8:58 ` [RFC PATCH 2/2] hwmon: (spd5118) Use generic parity calculation Wolfram Sang
2024-12-14 15:10 ` Guenter Roeck
2024-12-16 9:50 ` Geert Uytterhoeven
2024-12-17 8:16 ` Kuan-Wei Chiu
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=Z2E5H3-vNIi2_6oT@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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 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.