All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Jean Delvare" <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, "Przemysław Gaj" <pgaj@cadence.com>,
	linus@ucla.edu
Subject: Re: [PATCH RFT v2 0/5] i3c: introduce and use generic parity helper
Date: Sun, 5 Jan 2025 10:35:57 +0100	[thread overview]
Message-ID: <Z3pSfU2fNd12csNP@shikoro> (raw)
In-Reply-To: <Z3n-z5xA2ue8ojiF@yury-ThinkPad>

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

Hi Yury,

> Rasmus is reviewer. I'm - maintainer.

Oh, sorry. I just saw your both entries in MAINTAINERS and missed that
Rasmus has "R:" instead of "M:". No offence!

> I'm a bit doubted about adding a web link in sources because it may
> become invalid one day, but if Wolfram commits to maintain comments
> up-to-date, I'm OK with that.

I just added the page to the wayback machine. We could use this link
now: http://web.archive.org/web/20250105093316/https://funloop.org/codex/problem/parity/README.html

Better?

> I already acked the patch, so no need to ack it again.

Thanks!

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: "Alexandre Belloni" <alexandre.belloni@bootlin.com>,
	linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
	"Guenter Roeck" <linux@roeck-us.net>,
	"Jean Delvare" <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, "Przemysław Gaj" <pgaj@cadence.com>,
	linus@ucla.edu
Subject: Re: [PATCH RFT v2 0/5] i3c: introduce and use generic parity helper
Date: Sun, 5 Jan 2025 10:35:57 +0100	[thread overview]
Message-ID: <Z3pSfU2fNd12csNP@shikoro> (raw)
In-Reply-To: <Z3n-z5xA2ue8ojiF@yury-ThinkPad>


[-- Attachment #1.1: Type: text/plain, Size: 599 bytes --]

Hi Yury,

> Rasmus is reviewer. I'm - maintainer.

Oh, sorry. I just saw your both entries in MAINTAINERS and missed that
Rasmus has "R:" instead of "M:". No offence!

> I'm a bit doubted about adding a web link in sources because it may
> become invalid one day, but if Wolfram commits to maintain comments
> up-to-date, I'm OK with that.

I just added the page to the wayback machine. We could use this link
now: http://web.archive.org/web/20250105093316/https://funloop.org/codex/problem/parity/README.html

Better?

> I already acked the patch, so no need to ack it again.

Thanks!

   Wolfram


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 111 bytes --]

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2025-01-05  9:36 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29 10:12 [PATCH RFT v2 0/5] i3c: introduce and use generic parity helper Wolfram Sang
2024-12-29 10:12 ` Wolfram Sang
2024-12-29 10:12 ` [PATCH RFT v2 1/5] bitops: add generic parity calculation for u8 Wolfram Sang
2024-12-29 10:12   ` Wolfram Sang
2024-12-29 11:11   ` David Laight
2024-12-29 11:11     ` David Laight
2025-01-02  8:55     ` Wolfram Sang
2025-01-02  8:55       ` Wolfram Sang
2024-12-29 10:12 ` [PATCH RFT v2 2/5] hwmon: (spd5118) Use generic parity calculation Wolfram Sang
2024-12-29 10:12   ` Wolfram Sang
2024-12-29 10:12 ` [PATCH RFT v2 3/5] i3c: dw: use get_parity8 helper instead of open coding it Wolfram Sang
2024-12-29 10:12   ` Wolfram Sang
2024-12-29 10:12 ` [PATCH RFT v2 4/5] i3c: mipi-i3c-hci: " Wolfram Sang
2024-12-29 10:12   ` Wolfram Sang
2025-01-01 12:14   ` David Laight
2025-01-01 12:14     ` David Laight
2025-01-02  9:01     ` Wolfram Sang
2025-01-02  9:01       ` Wolfram Sang
2025-01-02 18:51       ` David Laight
2025-01-02 18:51         ` David Laight
2025-01-03 10:02         ` Wolfram Sang
2025-01-03 10:02           ` Wolfram Sang
2025-01-03 13:49           ` David Laight
2025-01-03 13:49             ` David Laight
2025-01-03 21:17             ` Wolfram Sang
2025-01-03 21:17               ` Wolfram Sang
2025-01-02 14:19   ` Jarkko Nikula
2025-01-02 14:19     ` Jarkko Nikula
2025-01-02 14:46     ` Wolfram Sang
2025-01-02 14:46       ` Wolfram Sang
2024-12-29 10:12 ` [PATCH RFT v2 5/5] i3c: cdns: " Wolfram Sang
2024-12-29 10:12   ` Wolfram Sang
2024-12-29 10:49   ` Geert Uytterhoeven
2024-12-29 10:49     ` Geert Uytterhoeven
2024-12-29 11:33     ` David Laight
2024-12-29 11:33       ` David Laight
2025-01-02  9:04     ` Wolfram Sang
2025-01-02  9:04       ` Wolfram Sang
2025-01-02  9:28       ` Geert Uytterhoeven
2025-01-02  9:28         ` Geert Uytterhoeven
2025-01-02  9:34         ` Wolfram Sang
2025-01-02  9:34           ` Wolfram Sang
2025-01-03 22:08           ` Alexandre Belloni
2025-01-03 22:08             ` Alexandre Belloni
2025-01-03 22:11 ` [PATCH RFT v2 0/5] i3c: introduce and use generic parity helper Alexandre Belloni
2025-01-03 22:11   ` Alexandre Belloni
2025-01-03 22:16   ` Wolfram Sang
2025-01-03 22:16     ` Wolfram Sang
2025-01-05  3:38     ` Yury Norov
2025-01-05  3:38       ` Yury Norov
2025-01-05  9:35       ` Wolfram Sang [this message]
2025-01-05  9:35         ` Wolfram Sang

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=Z3pSfU2fNd12csNP@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=jdelvare@suse.com \
    --cc=linus@ucla.edu \
    --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 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.