> -----Original Message-----
> From: Vladimir Oltean <vladimir.olt...@nxp.com>
> Sent: Tuesday, October 29, 2024 6:31 PM
> To: net...@vger.kernel.org; Radu-Andrei Bulie <radu-andrei.bu...@nxp.com>
> Cc: David S. Miller <da...@davemloft.net>; Eric Dumazet
> <eduma...@google.com>; Jakub Kicinski <k...@kernel.org>; Paolo Abeni
> <pab...@redhat.com>; Breno Leitao <lei...@debian.org>; Madalin Bucur
> <madalin.bu...@nxp.com>; Ioana Ciornei <ioana.cior...@nxp.com>; Christophe
> Leroy <christophe.le...@csgroup.eu>; Sean Anderson
> <sean.ander...@linux.dev>; linux-ker...@vger.kernel.org; linuxppc-
> d...@lists.ozlabs.org; linux-arm-ker...@lists.infradead.org
> Subject: [PATCH net] net: dpaa_eth: print FD status in CPU endianness in
> dpaa_eth_fd tracepoint
>
> Sparse warns:
>
> note: in included file (through ../include/trace/trace_events.h,
> ../include/trace/define_trace.h,
> ../drivers/net/ethernet/freescale/dpaa/dpaa_eth_trace.h):
> warning: incorrect type in assignment (different base types)
> expected unsigned int [usertype] fd_status
> got restricted __be32 const [usertype] status
>
> We take struct qm_fd :: status, store it and print it as an u32,
> though it is a big endian field. We should print the FD status in
> CPU endianness for ease of debug and consistency between PowerPC and
> Arm systems.
>
> Though it is a not often used debug feature, it is best to treat it as
> a bug and backport the format change to all supported stable kernels,
> for consistency.
>
> Fixes: eb11ddf36eb8 ("dpaa_eth: add trace points")
> Signed-off-by: Vladimir Oltean <vladimir.olt...@nxp.com>
> ---
> Context:
> https://lore.kernel.org/oe-kbuild-all/20241028-sticky-refined-lionfish-
> b06c0c@leitao/
Acked-by: Madalin Bucur <madalin.bu...@oss.nxp.com>
