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 AC4AACA5FE0 for ; Fri, 2 Oct 2026 10:44:06 +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=RzEk1S+4nHmU4W3a5wiCXap5Wv 61/m/yDoj72dD1S7n/m3J2BsYBUeluoOk3x19Fb8Y+Fzfk9qRJW77QDke9z//69x9DH8V0W34SIA7 cPahNrwcBYvaogD5oriUVqOI4QtMrmbLCgVuZyCd+jnTcmJ+x9NAGEKJY4Kia/4SfVVJGDZBAJL/6 XvVN9/VtS2NySk6fGFYIJ7DiBMQ2ayX538Mw/q/ciIhh7u9+EWqPvxGuO+HeLvdBc3px6ztm64Nu4 lgL88xA8A9efsKVvQceYP2Xywao81VCFFcCcKrbHxPDkgyFUsXjlOHwBABVkZXuF7j5czetoZUHrd z7wpJHew==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xCakC-0000000BMSQ-2XTN; Fri, 02 Oct 2026 10:44:00 +0000 Received: from sea.source.kernel.org ([172.234.252.31]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xCakB-0000000BMSG-1Fd0 for linux-arm-kernel@lists.infradead.org; Fri, 02 Oct 2026 10:43:59 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id ED117404C8; Fri, 2 Oct 2026 10:43:58 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4121B1F000FF; Fri, 2 Oct 2026 10:43:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790937838; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=eIR15wHiYZiY34E1o2sMCBcTHueo2onmVlE9AJyntqY9Z6GuOeV9rEeFKelWW7eoj NKJIecG71cAU/Bt91bZTaLjXf2wgNNoKHQv0WyWiz295QBWNLvcyo/rDbo5Lgq1f6e 9uGOuVvXj+hacqpO9iobknLHQyHjPstI7NtTVttK+dVZg5yNnS3IQLMZjzMHgmuesw gWO5rsZeHYcfudSNTY/uV4F422OcF03lPJQDR2MK6upAq9T4QmVG5XvhdWkD+g/EJu 1oiZI4bc4Q4iLnuqw+C13FXMW0BPHQ88eeOGUnE1kS+QTGvBUccwRVT+cizmXZcH1x XY49Cxj7yOK/Q== 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 , netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH net] net: stmmac: serialize PTP timestamping configuration with priv->lock Date: Fri, 02 Oct 2026 10:43:57 +0000 Message-ID: <179093783778.1402591.4305443516462782245@kernel.org> In-Reply-To: <20261002-stmmac-hwtstamp-missing-lock-v1-1-189ce151a624@oss.qualcomm.com> References: <20261002-stmmac-hwtstamp-missing-lock-v1-1-189ce151a624@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.