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 E4646CA5FF0 for ; Mon, 5 Oct 2026 08:13:15 +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=sAYKQk/mNPjRAwKl+CFGJCYaNR PWRpnQ6J2ZjI6vVVSpnmb2edr8rdVT0J+B6J04aAyx8qBGzZDbqG46fcvxYJzydCGu8xzMV2ad2Qy AaiAVY/603jsf1F6CxB8Fes0TRFsBlIRJUAzSRww15VpN3Uwz8viRKr8sFj5SkW8NPrpj9HyY/Jf0 oONF0AFtpQDwMQ2Yk835vvnq2gK0QpHlC/Zd2d4cMMbFkugRAE+DEX112y4eJD0roBkovDRGGyoXc zh+xIhnRh2KkthYIUbZZgHChLGnV2pi0Ct2JzQdtozIA7cPNJacWvDQUK6YosDOvYqqdvy0op5iFR e9hZAVmg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xDdor-0000000Fr72-1CNr; Mon, 05 Oct 2026 08:13:09 +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 1xDdoq-0000000Fr6J-0bMu for linux-arm-kernel@lists.infradead.org; Mon, 05 Oct 2026 08:13:08 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id 72C5140BE2; Mon, 5 Oct 2026 08:13:07 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A36AE1F000FF; Mon, 5 Oct 2026 08:13:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791187987; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=a/+McXrI/vIahDkaWRmWg2qkjYMubKGdTmVTplBucoCiMlW34vm5/yPlpqNu1taca o9ZQLOwyC4eqOaM3s87hie7OfjgNOwFJ4/FasFjRaxnva+tcVGJ2A+PFFpJMkaO9PW bkht54uJDQHXVPdGRO4WSrBWFhTs+hT9ONquY0rZ0DmPRlu3NwrldUkv17loyje0LM mKr9DA0bIVXAOK4WnX2Scfg3SL8GjxRd04bDSWFcOmQY3Q8m17r4WHall+XFQFHaQW /K6AoPboOG5SqmZB1euOzWpYE7bslp2V6hpoBGqQjZ3KnuAWp+pLgOrgP5z1z36Dux SNzeB/XIY36zw== 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 , "Russell King (Oracle)" , Kory Maincent , netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH net v2] net: stmmac: serialize PTP timestamping configuration with priv->lock Date: Mon, 05 Oct 2026 08:13:06 +0000 Message-ID: <179118798620.1402591.3969606322694204017@kernel.org> In-Reply-To: <20261005-stmmac-hwtstamp-missing-lock-v2-1-3b3bf4fe3f45@oss.qualcomm.com> References: <20261005-stmmac-hwtstamp-missing-lock-v2-1-3b3bf4fe3f45@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.