From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6137922EED for ; Wed, 4 Oct 2023 21:12:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Qj61GGKA" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3CB4BC433C8; Wed, 4 Oct 2023 21:12:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1696453973; bh=UMkpK8hBnhmZu6SDCnn6+NldPVpXde3GUYG3ar+O4pA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Qj61GGKAoLT8aQBhpkE8fQcl8WRuwzwUwJhClfjpCgKfNNb8mr8kRzzH0etrJC/Rq 4rc2WQEpWlvtffsq83jsTASvbJp5x8TV2tgMymVxvn/18vUn7Vnq082VOoMG9834Vt nfPlOVSMmoVlSrxr0A0Wox7b3MuHsYum/BpvJPphv0k6FyLg8GDQIRJiNnM7VXxTvo M8BSgH1cmX4XnYvllRfczK9nFVOkrJfR3aJOnk9JDfM2BSpR6AVt1CAh/PnbbzbkIG hozI2fgP7ivkjyzdYPMr+nm42glxiHu6RR1kuqpG+h/MPq6LL3L4UFU78Aq0+hPU46 CZVQ3W1QUwa9g== Date: Wed, 4 Oct 2023 14:12:52 -0700 From: Jakub Kicinski To: Sai Krishna Cc: , , , , , , , , , , , Subject: Re: [net PATCH] octeontx2-af: Enable hardware timestamping for VFs Message-ID: <20231004141252.49812e65@kernel.org> In-Reply-To: <20230929071621.853570-1-saikrishnag@marvell.com> References: <20230929071621.853570-1-saikrishnag@marvell.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 29 Sep 2023 12:46:21 +0530 Sai Krishna wrote: > Subject: [net PATCH] octeontx2-af: Enable hardware timestamping for VFs > Date: Fri, 29 Sep 2023 12:46:21 +0530 > X-Mailer: git-send-email 2.25.1 > > Currently for VFs, mailbox returns error when hardware timestamping enable > is requested. This patch fixes this issue. > > Fixes: 421572175ba5 ("octeontx2-af: Support to enable/disable HW timestamping") If it never worked for VFs but worked for PFs - it's not really a fix. New functionality enablement is -next material, even if the fact that it was previously disable was unintentional. -- pw-bot: cr