From: David Miller <davem@davemloft.net>
To: yangbo.lu@nxp.com
Cc: netdev@vger.kernel.org, richardcochran@gmail.com,
claudiu.manoil@nxp.com, shawnguo@kernel.org, robh+dt@kernel.org,
alexandru.marginean@nxp.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2, 0/4] ENETC: support hardware timestamping
Date: Fri, 24 May 2019 13:16:50 -0700 (PDT) [thread overview]
Message-ID: <20190524.131650.1001639096871571503.davem@davemloft.net> (raw)
In-Reply-To: <20190523023451.2933-1-yangbo.lu@nxp.com>
From: "Y.b. Lu" <yangbo.lu@nxp.com>
Date: Thu, 23 May 2019 02:33:24 +0000
> This patch-set is to support hardware timestamping for ENETC
> and also to add ENETC 1588 timer device tree node for ls1028a.
>
> Because the ENETC RX BD ring dynamic allocation has not been
> supported and it is too expensive to use extended RX BDs
> if timestamping is not used, a Kconfig option is used to
> enable extended RX BDs in order to support hardware
> timestamping. This option will be removed once RX BD
> ring dynamic allocation is implemented.
Series applied.
prev parent reply other threads:[~2019-05-24 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 2:33 [PATCH net-next v2, 0/4] ENETC: support hardware timestamping Y.b. Lu
2019-05-23 2:33 ` [PATCH net-next v2, 1/4] enetc: add hardware timestamping support Y.b. Lu
2019-05-23 2:33 ` [PATCH net-next v2, 2/4] enetc: add get_ts_info interface for ethtool Y.b. Lu
2019-05-23 2:33 ` [PATCH net-next v2, 3/4] dt-binding: ptp_qoriq: support ENETC PTP compatible Y.b. Lu
2019-05-23 2:33 ` [PATCH net-next v2, 4/4] arm64: dts: fsl: ls1028a: add ENETC 1588 timer node Y.b. Lu
2019-05-23 13:48 ` [PATCH net-next v2, 0/4] ENETC: support hardware timestamping Richard Cochran
2019-05-24 2:20 ` Y.b. Lu
2019-05-24 20:16 ` David Miller [this message]
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=20190524.131650.1001639096871571503.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandru.marginean@nxp.com \
--cc=claudiu.manoil@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=yangbo.lu@nxp.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