From: "Heiko Stübner" <heiko@sntech.de>
To: Andi Shyti <andi@smida.it>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Qianfeng Rong <rongqianfeng@vivo.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Khalil Blaiech <kblaiech@nvidia.com>,
Asmaa Mnebhi <asmaa@nvidia.com>,
Andi Shyti <andi.shyti@kernel.org>,
Qii Wang <qii.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Linus Walleij <linusw@kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH v1 5/7] i2c: rk3x: Use HZ_PER_GHZ constant instead of plain number
Date: Tue, 13 Jan 2026 16:10:01 +0100 [thread overview]
Message-ID: <2063916.2IRrRt1zHL@diego> (raw)
In-Reply-To: <20260112134900.4142954-6-andriy.shevchenko@linux.intel.com>
Am Montag, 12. Januar 2026, 14:46:13 Mitteleuropäische Normalzeit schrieb Andy Shevchenko:
> Use defined constant to avoid the possible mistakes and to provide
> an additional information on the units.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Andi Shyti <andi@smida.it>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Qianfeng Rong <rongqianfeng@vivo.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Khalil Blaiech <kblaiech@nvidia.com>,
Asmaa Mnebhi <asmaa@nvidia.com>,
Andi Shyti <andi.shyti@kernel.org>,
Qii Wang <qii.wang@mediatek.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Linus Walleij <linusw@kernel.org>,
Patrice Chotard <patrice.chotard@foss.st.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH v1 5/7] i2c: rk3x: Use HZ_PER_GHZ constant instead of plain number
Date: Tue, 13 Jan 2026 16:10:01 +0100 [thread overview]
Message-ID: <2063916.2IRrRt1zHL@diego> (raw)
In-Reply-To: <20260112134900.4142954-6-andriy.shevchenko@linux.intel.com>
Am Montag, 12. Januar 2026, 14:46:13 Mitteleuropäische Normalzeit schrieb Andy Shevchenko:
> Use defined constant to avoid the possible mistakes and to provide
> an additional information on the units.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-01-13 15:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 13:46 [PATCH v1 0/7] i2c: busses: Introduce and use HZ_PER_GHZ Andy Shevchenko
2026-01-12 13:46 ` Andy Shevchenko
2026-01-12 13:46 ` [PATCH v1 1/7] units: Add HZ_PER_GHZ Andy Shevchenko
2026-01-12 13:46 ` Andy Shevchenko
2026-01-12 15:48 ` Linus Walleij
2026-01-12 15:48 ` Linus Walleij
2026-01-13 14:23 ` Andi Shyti
2026-01-13 14:23 ` Andi Shyti
2026-01-12 13:46 ` [PATCH v1 2/7] i2c: mlxbf: Use HZ_PER_GHZ constant instead of custom one Andy Shevchenko
2026-01-12 13:46 ` Andy Shevchenko
2026-01-12 13:46 ` [PATCH v1 3/7] i2c: mt65xx: Use HZ_PER_GHZ constant instead of plain number Andy Shevchenko
2026-01-12 13:46 ` Andy Shevchenko
2026-01-12 13:46 ` [PATCH v1 4/7] i2c: nomadik: " Andy Shevchenko
2026-01-12 13:46 ` Andy Shevchenko
2026-01-12 15:52 ` Linus Walleij
2026-01-12 15:52 ` Linus Walleij
2026-01-12 13:46 ` [PATCH v1 5/7] i2c: rk3x: " Andy Shevchenko
2026-01-12 13:46 ` Andy Shevchenko
2026-01-13 15:10 ` Heiko Stübner [this message]
2026-01-13 15:10 ` Heiko Stübner
2026-01-12 13:46 ` [PATCH v1 6/7] i2c: st: " Andy Shevchenko
2026-01-12 13:46 ` Andy Shevchenko
2026-01-13 15:29 ` Patrice CHOTARD
2026-01-13 15:29 ` Patrice CHOTARD
2026-01-12 13:46 ` [PATCH v1 7/7] i2c: synquacer: " Andy Shevchenko
2026-01-12 13:46 ` Andy Shevchenko
2026-01-12 16:15 ` [PATCH v1 0/7] i2c: busses: Introduce and use HZ_PER_GHZ AngeloGioacchino Del Regno
2026-01-12 16:15 ` AngeloGioacchino Del Regno
2026-01-13 15:28 ` Wolfram Sang
2026-01-13 15:28 ` Wolfram Sang
2026-01-14 7:36 ` Andi Shyti
2026-01-14 7:36 ` Andi Shyti
2026-01-14 8:23 ` Andy Shevchenko
2026-01-14 8:23 ` Andy Shevchenko
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=2063916.2IRrRt1zHL@diego \
--to=heiko@sntech.de \
--cc=andi.shyti@kernel.org \
--cc=andi@smida.it \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ardb@kernel.org \
--cc=asmaa@nvidia.com \
--cc=kblaiech@nvidia.com \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=patrice.chotard@foss.st.com \
--cc=qii.wang@mediatek.com \
--cc=rongqianfeng@vivo.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.