From: Richard Cochran <richardcochran@gmail.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
devicetree@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Miroslav Lichvar <mlichvar@redhat.com>,
Murali Karicheri <m-karicheri2@ti.com>,
Rob Herring <robh+dt@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Wingman Kwok <w-kwok2@ti.com>
Subject: Re: [PATCH V6 net-next 11/11] ptp: Add a driver for InES time stamping IP core.
Date: Mon, 16 Dec 2019 20:34:33 -0800 [thread overview]
Message-ID: <20191217043433.GA1363@localhost> (raw)
In-Reply-To: <20191216161114.3604d45d@cakuba.netronome.com>
On Mon, Dec 16, 2019 at 04:11:14PM -0800, Jakub Kicinski wrote:
> On Mon, 16 Dec 2019 08:13:26 -0800, Richard Cochran wrote:
> > + clkid = (u64 *)(data + offset + OFF_PTP_CLOCK_ID);
> > + portn = (u16 *)(data + offset + OFF_PTP_PORT_NUM);
> > + seqid = (u16 *)(data + offset + OFF_PTP_SEQUENCE_ID);
>
> These should perhaps be __be types?
>
> Looks like there is a few other sparse warnings in ptp_ines.c, would
> you mind addressing those?
I saw the sparse warnings before (from one of the robots), but I
decided that they are false positives. Or perhaps I don't appreciate
what the warnings mean...
Take the 'clkid' pointer for example:
> > + if (cpu_to_be64(ts->clkid) != *clkid) {
> > + pr_debug("clkid mismatch ts %llx != skb %llx\n",
> > + cpu_to_be64(ts->clkid), *clkid);
> > + return false;
> > + }
The field that to which 'clkid' points is in network byte order. The
code correctly converts ts->clkid (in CPU byte order) to network byte
order before comparing it with the field.
So where is the error?
Thanks,
Richard
next prev parent reply other threads:[~2019-12-17 4:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 16:13 [PATCH V6 net-next 00/11] Peer to Peer One-Step time stamping Richard Cochran
2019-12-16 16:13 ` [PATCH V6 net-next 01/11] net: phy: Introduce helper functions for time stamping support Richard Cochran
2019-12-17 9:01 ` Andrew Lunn
2019-12-16 16:13 ` [PATCH V6 net-next 02/11] net: macvlan: Use the PHY time stamping interface Richard Cochran
2019-12-17 8:59 ` Andrew Lunn
2019-12-16 16:13 ` [PATCH V6 net-next 03/11] net: vlan: " Richard Cochran
2019-12-17 9:01 ` Andrew Lunn
2019-12-16 16:13 ` [PATCH V6 net-next 04/11] net: ethtool: " Richard Cochran
2019-12-17 9:01 ` Andrew Lunn
2019-12-16 16:13 ` [PATCH V6 net-next 05/11] net: netcp_ethss: " Richard Cochran
2019-12-17 9:03 ` Andrew Lunn
2019-12-16 16:13 ` [PATCH V6 net-next 06/11] net: Introduce a new MII " Richard Cochran
2019-12-17 9:21 ` Andrew Lunn
2019-12-20 14:57 ` Richard Cochran
2019-12-20 15:33 ` Andrew Lunn
2019-12-20 18:01 ` Richard Cochran
2019-12-20 23:11 ` David Miller
2019-12-16 16:13 ` [PATCH V6 net-next 07/11] net: Add a layer for non-PHY MII time stamping drivers Richard Cochran
2019-12-16 16:13 ` [PATCH V6 net-next 08/11] dt-bindings: ptp: Introduce MII time stamping devices Richard Cochran
2019-12-17 15:17 ` Andrew Lunn
2019-12-18 20:03 ` Rob Herring
2019-12-19 4:13 ` Richard Cochran
2019-12-18 20:02 ` Rob Herring
2019-12-16 16:13 ` [PATCH V6 net-next 09/11] net: mdio: of: Register discovered MII time stampers Richard Cochran
2019-12-17 15:19 ` Andrew Lunn
2019-12-18 20:05 ` Rob Herring
2019-12-16 16:13 ` [PATCH V6 net-next 10/11] net: Introduce peer to peer one step PTP time stamping Richard Cochran
2019-12-16 16:13 ` [PATCH V6 net-next 11/11] ptp: Add a driver for InES time stamping IP core Richard Cochran
2019-12-17 0:11 ` Jakub Kicinski
2019-12-17 4:34 ` Richard Cochran [this message]
2019-12-17 17:18 ` Jakub Kicinski
2019-12-17 15:33 ` Andrew Lunn
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=20191217043433.GA1363@localhost \
--to=richardcochran@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jacob.e.keller@intel.com \
--cc=jakub.kicinski@netronome.com \
--cc=m-karicheri2@ti.com \
--cc=mark.rutland@arm.com \
--cc=mlichvar@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=w-kwok2@ti.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).