From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C8ED8CA5FA5 for ; Tue, 29 Sep 2026 13:15:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:MIME-Version: Content-Transfer-Encoding:Content-Type:References:In-Reply-To:Message-ID:Date :Subject:Cc:To:From:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; b=QfbaRPL3S9nJwvvgKoqvgyFJw9 8NOrWManLW1n1jCT6YPYR5aRxchL7s9kE+Z9tMfIZLF017ld6/oDjJTdaa1/sJkVYZHRDcdPG8MK1 nJQFI4QN3hTB7PiBnS07JHnSO0sgI9oY7H1qPekPacoPq9FT0Vq+LzQVw4+Bpu2FXWdR8d2f95YyX 3z+TGIclsBvABFcxFMUDwh8rZBZD+TGJejpjDEm7e6o0+1rYS6hY+9HaT5ewZBIugRpaWYOAPEBp3 zwas8t6JoWlDL9WEJJP6cqDh63fUmmjvFcHjqTfdmp75Ot4FvmDwcNFwtPrTM/KqkwZgGUpeePMON FD9h0RGQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xBXfZ-00000003e71-0tmR; Tue, 29 Sep 2026 13:14:53 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xBXfY-00000003e6c-16NU for linux-arm-kernel@lists.infradead.org; Tue, 29 Sep 2026 13:14:52 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id B406A41377; Tue, 29 Sep 2026 13:14:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E4E791F000FF; Tue, 29 Sep 2026 13:14:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790687691; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=SaOLiz/P4QD/1jWp3xRrQOu8XJphhx/BdMpkQNQOX3+mkiZkQg4BkPvmvL57yXfYK u2iAtsiM6mNzKOyKD4g2nd91CwQXWGXw7wVvHyH6liP/8lpgPK5O01G1uOa+pqM7Pe CLt4AVcZj+eosxPCk/HYVPGlBBHiEAN7+WtPclD499vr18ETJL26iGeNp/qdE1zTYy iFxJDkMq46ZzowfTy9gdCKVh1IgXxzL713ZAVGcdJCiyCYTDtt97K96u4hCnT+nmDk 9L2Yr1rxi+NfDKl/h0Y6q82Yz+Q1psVKtr6wcobB88D/cEjKsV/iKN8B/xykxlep1s Mu+fE7ApLYg9A== From: netdev-bot+sinfo@kernel.org To: Lorenzo Bianconi Cc: Maxime Chevallier , Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Maxime Coquelin , Alexandre Torgue , Richard Cochran , Jose Abreu , netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH net v3] net: stmmac: propagate PTP addend and system time programming errors Date: Tue, 29 Sep 2026 13:14:50 +0000 Message-ID: <179068769042.31693.17699965363723906103@kernel.org> In-Reply-To: <20260929-stmmac-ptp-added-systime-error-v3-1-ddd6afe936b4@oss.qualcomm.com> References: <20260929-stmmac-ptp-added-systime-error-v3-1-ddd6afe936b4@oss.qualcomm.com> Auto-Submitted: auto-generated Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi! This is an automated message. This series looks like a fix, but its commit messages seem to be missing some information: - How the issue was discovered, e.g. hit in production, hit during development, syzbot report, manual code inspection, LLM or static analysis tool scan. - Whether the issue was actually triggered, or is only theoretical (e.g. found by code inspection). If it was triggered please include the symptoms, like the stack trace or error messages. - What hardware the change was tested on. For driver fixes please mention the device (and if relevant firmware version) used for testing, or say that the change was not tested on real hardware. Please do not repost the series just to address the above. Instead, reply to this email with the missing information, so that reviewers can take it into account. If the series needs another revision for other reasons, please include the information in the commit messages then. The evaluation is done by an LLM so it may be wrong, if you think that is the case please reply and explain.