LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Claudiu Manoil <claudiu.manoil@nxp.com>
To: "Y.b. Lu" <yangbo.lu@nxp.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Richard Cochran <richardcochran@gmail.com>,
	David Miller <davem@davemloft.net>,
	Shawn Guo <shawnguo@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/3] enetc: add hardware timestamping support
Date: Thu, 16 May 2019 13:31:12 +0000	[thread overview]
Message-ID: <VI1PR04MB4880C3E6D24AB7A53887D9C9960A0@VI1PR04MB4880.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190516100028.48256-2-yangbo.lu@nxp.com>

>-----Original Message-----
>From: Y.b. Lu
[...]
>Subject: [PATCH 1/3] enetc: add hardware timestamping support
>
[...]

Hi Yangbo,

These enetc patches targeting net-next will have to be rebased on
the latest enetc net.git commits, otherwise there will be some merge
conflicts for enetc.c and enetc_ethtool.c.
Thanks,
Claudiu

see
22fb43f36006 "enetc: Add missing link state info for ethtool"
f4a0be84d73e "enetc: Fix NULL dma address unmap for Tx BD extensions"


  reply	other threads:[~2019-05-16 13:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  9:59 [PATCH 0/3] ENETC: support hardware timestamping Y.b. Lu
2019-05-16  9:59 ` [PATCH 1/3] enetc: add hardware timestamping support Y.b. Lu
2019-05-16 13:31   ` Claudiu Manoil [this message]
2019-05-20  2:55     ` Y.b. Lu
2019-05-16 14:32   ` Richard Cochran
2019-05-16 15:30     ` Claudiu Manoil
2019-05-20  3:25       ` Y.b. Lu
2019-05-20  3:20     ` [EXT] " Y.b. Lu
2019-05-20  4:41       ` Richard Cochran
2019-05-16  9:59 ` [PATCH 2/3] enetc: add get_ts_info interface for ethtool Y.b. Lu
2019-05-16  9:59 ` [PATCH 3/3] arm64: dts: fsl: ls1028a: add ENETC 1588 timer node Y.b. Lu

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=VI1PR04MB4880C3E6D24AB7A53887D9C9960A0@VI1PR04MB4880.eurprd04.prod.outlook.com \
    --to=claudiu.manoil@nxp.com \
    --cc=davem@davemloft.net \
    --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;
as well as URLs for NNTP newsgroup(s).