From: MD Danish Anwar <danishanwar@ti.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Roger Quadros <rogerq@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>, <imx@lists.linux.dev>
Subject: Re: [PATCH net-next 1/5] net: ti: icssg-prueth: Do not print physical memory addresses
Date: Mon, 13 Jan 2025 13:33:28 +0530 [thread overview]
Message-ID: <e08733fc-3dca-43e8-bcb6-c7d86c9f0982@ti.com> (raw)
In-Reply-To: <20250112-syscon-phandle-args-net-v1-1-3423889935f7@linaro.org>
On 12/01/25 7:02 pm, Krzysztof Kozlowski wrote:
> Debugging messages should not reveal anything about memory addresses.
> This also solves arm compile test warnings:
>
> drivers/net/ethernet/ti/icssg/icssg_prueth_sr1.c:1034:49: error:
> format specifies type 'unsigned long long' but the argument has type 'phys_addr_t' (aka 'unsigned int') [-Werror,-Wformat]
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: MD Danish Anwar <danishanwar@ti.com>
--
Thanks and Regards,
Danish
next prev parent reply other threads:[~2025-01-13 8:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 13:32 [PATCH net-next 0/5] net: ethernet: Simplify few things Krzysztof Kozlowski
2025-01-12 13:32 ` [PATCH net-next 1/5] net: ti: icssg-prueth: Do not print physical memory addresses Krzysztof Kozlowski
2025-01-13 8:03 ` MD Danish Anwar [this message]
2025-01-12 13:32 ` [PATCH net-next 2/5] net: ti: icssg-prueth: Use syscon_regmap_lookup_by_phandle_args Krzysztof Kozlowski
2025-01-13 8:07 ` MD Danish Anwar
2025-01-13 11:04 ` Krzysztof Kozlowski
2025-01-15 2:06 ` Jakub Kicinski
2025-01-12 13:32 ` [PATCH net-next 3/5] net: stmmac: imx: " Krzysztof Kozlowski
2025-01-12 13:32 ` [PATCH net-next 4/5] net: stmmac: sti: " Krzysztof Kozlowski
2025-01-12 13:32 ` [PATCH net-next 5/5] net: stmmac: stm32: " Krzysztof Kozlowski
2025-01-13 8:05 ` Yanteng Si
2025-01-13 11:08 ` Krzysztof Kozlowski
2025-01-13 17:01 ` Andrew Lunn
2025-01-14 1:58 ` Yanteng Si
2025-01-15 2:10 ` [PATCH net-next 0/5] net: ethernet: Simplify few things patchwork-bot+netdevbpf
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=e08733fc-3dca-43e8-bcb6-c7d86c9f0982@ti.com \
--to=danishanwar@ti.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=joabreu@synopsys.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rogerq@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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