[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e2e26d30-86fb-4005-9a0e-ac9b793df86a@lunn.ch>
Date: Fri, 25 Aug 2023 15:50:06 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Radu Pirea (OSS)" <radu-nicolae.pirea@....nxp.com>
Cc: Sabrina Dubroca <sd@...asysnail.net>, hkallweit1@...il.com,
linux@...linux.org.uk, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, richardcochran@...il.com,
sebastian.tobuschat@....com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC net-next v2 3/5] net: phy: nxp-c45-tja11xx add MACsec
support
> > > > +static bool nxp_c45_rx_sc_valid(struct nxp_c45_secy *phy_secy,
> > > > + struct macsec_rx_sc *rx_sc)
> > > > +{
> > > > + u16 port = (__force u64)rx_sc->sci >> (ETH_ALEN * 8);
> > >
> > > u64 sci = be64_to_cpu((__force __be64)rx_sc->sci);
> >
> > why is the __force needed? What happens with a normal cast?
> >
>
> Sparse will print warnings if __force is missing.
What is the warning? I just want to make sure __force is the correct
solution, not that something has the wrong type and we should be
fixing a design issue.
Andrew
Powered by blists - more mailing lists