drm/omap: Use correct printk format specifiers for size_t

The correct format specifier for size_t is %zu. Using %d (or %u)
generates a warning on 64-bit platforms. Fix it.

Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
This commit is contained in:
Laurent Pinchart 2021-07-28 18:16:15 +03:00
parent 753f2674ad
commit d6a4bf45a9
1 changed files with 2 additions and 2 deletions

View File

@ -2094,7 +2094,7 @@ static int dsi_vc_send_long(struct dsi_data *dsi, int vc,
u8 b1, b2, b3, b4; u8 b1, b2, b3, b4;
if (dsi->debug_write) if (dsi->debug_write)
DSSDBG("dsi_vc_send_long, %d bytes\n", msg->tx_len); DSSDBG("dsi_vc_send_long, %zu bytes\n", msg->tx_len);
/* len + header */ /* len + header */
if (dsi->vc[vc].tx_fifo_size * 32 * 4 < msg->tx_len + 4) { if (dsi->vc[vc].tx_fifo_size * 32 * 4 < msg->tx_len + 4) {
@ -2390,7 +2390,7 @@ static int dsi_vc_generic_read(struct omap_dss_device *dssdev, int vc,
return 0; return 0;
err: err:
DSSERR("%s(vc %d, reqlen %d) failed\n", __func__, vc, msg->tx_len); DSSERR("%s(vc %d, reqlen %zu) failed\n", __func__, vc, msg->tx_len);
return r; return r;
} }