Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp896554ybi; Fri, 24 May 2019 13:18:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqy531V2TUS3feAF60UrKsA+kP/BQfH19pN+i8rkQ/0HLO3T7TpMm1h1zi8mpOmxiLXcMx93 X-Received: by 2002:a17:90a:1b48:: with SMTP id q66mr11953381pjq.114.1558729135310; Fri, 24 May 2019 13:18:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1558729135; cv=none; d=google.com; s=arc-20160816; b=jNHXcjF9wRuebN9NKAFXwA2U/c5gf7QSAMVhnLsu5OBtFNLhrIkRdJ20D1v8+W72va QbFLh743FzzCKxketRuQIRAIR0sOynQ+SLBJHmJuZHK2wEjYy1JSrxDccvze63lFQK+u rzJ3yl5dQtTsKqBz1k0sn8l+YjGOkh0E4M2Ef2pjPmQzrzttV/mQh9br9oWH4hvrnDhN 3AWlGTVaeg42QH/8cn+hotcJ1fO0tgzUjClcc61JwbYzDlOWV7JdHIydw0arXJfWudFc oa1yVVx/rcyDMnCAwQCzMlLRvBAvpWsF2HV5zdPa87qL3t3mpkrgEcD+EViwY2dlSMF1 AvRw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=vhOKeQ2ogvAXFjL36Q9WkOxoroHltRoPUsuW8gsNPq0=; b=sHeltmhWK7L413n7/S9jzCAGXpKC8QjAOS6s8NmFUPqDtwdoL9V559g78QeoYnXrOd 7ycZUjh8Mzz1PcwGsowPfUqP/EEnccL0hlSM2iyi0sg3VA0UQUoAMZ73DMGbDSGv5p11 Ox+iyXMST09aiGbFoyAmiIInBkPAXYeWq73QTqmUVRHYke98VAUD0AGI0ioL6P2rE5cP 5IuQg071Qmwgnf1x6ax1eOnFt+ORDJ5rGpvwdqmMwamv6xpLVNe0f7ymz9VXqykq5w1+ fFYebp2kDxftlwld02XZfQ1seWnXyY+jlZJsRLy+feQcjv/UZ/NScb3Ejvf3yJevCFHo F9Vg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o18si5009422pjp.88.2019.05.24.13.18.39; Fri, 24 May 2019 13:18:55 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404054AbfEXUQw (ORCPT + 99 others); Fri, 24 May 2019 16:16:52 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:42590 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391739AbfEXUQw (ORCPT ); Fri, 24 May 2019 16:16:52 -0400 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::3d8]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 6363514DE103B; Fri, 24 May 2019 13:16:51 -0700 (PDT) Date: Fri, 24 May 2019 13:16:50 -0700 (PDT) Message-Id: <20190524.131650.1001639096871571503.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 From: David Miller In-Reply-To: <20190523023451.2933-1-yangbo.lu@nxp.com> References: <20190523023451.2933-1-yangbo.lu@nxp.com> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Fri, 24 May 2019 13:16:51 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "Y.b. Lu" 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.