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 1B7CDCA9EC5 for ; Mon, 12 Oct 2026 15:30:57 +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=38kCfEsA3n1r4yaseZkXBQU6ws Mroh4DeZ+mXKFVhdrtIaSOJCtfSnEKWzb0l6DznRJpoA64y81ICuiVlEjnUyf0QSG+f4y3cWw5q47 Ci3Ckf0jwAYvePctZlqhbOzV4W3VxCNsbI/SwrGab+f2uRDopFCKMd1uh7upbd8pt/PyhiHqeHmR4 +54Hm0dcbxF6zXHCqsrVYZg8+M6GRKjdqDj7kMOjf+UUgY780/ymcnyx75XDEJ9962XH29eUE0cJq DvK99FkwfPZkoaRHLkg4GyZGW7pS1aRdMBcMk/9DjVpb1oBlxy5LBWVRoYD+VtY/zCGJhmE6qDy+p CwaibbUw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xGHzG-0000000AoAk-1rt1; Mon, 12 Oct 2026 15:30:50 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xGHzF-0000000AoAV-2UNV for linux-arm-kernel@lists.infradead.org; Mon, 12 Oct 2026 15:30:49 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 0C0DF602D1; Mon, 12 Oct 2026 15:30:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D41501F0089C; Mon, 12 Oct 2026 15:30:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791819048; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=hKkW2znF0TQvi5ugzZKk3qwCJSKhgDn4ZbnNdIwbIibdCq/pKY99M/ZLYeb8txmQM GNGFiFMtmBC43gCUqrptLkqvs5u3CyTnRk5huMQq7q0iP9e6oLxiCyrxpdNqtTE1WD PQMXUU6UP3Iv54/gGqCM22HbgQ9Bm4Pxd90ix+6wRvtJuXCBzDEGt7P/5dlRtxvUfJ YNEIAPB4bcpNdgVP4Mj5o7YsVadjXVyGY7yrjSl5ifvumoCaFWJKX+vT0ZIFnbmfMJ k/7H6CzeFz8HxCfvW/NtEtwNjwphmiYvsfHq+/MYs+tNV5h8ViAnxnG/x2mz6z1US1 Hl6itQDYej2rw== 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 , Alexei Starovoitov , Daniel Borkmann , Jesper Dangaard Brouer , John Fastabend , Stanislav Fomichev , Ong Boon Leong , netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, bpf@vger.kernel.org Subject: Re: [PATCH net-next 0/2] stmmac: some XDP fixes in XDP_TX path Date: Mon, 12 Oct 2026 15:30:47 +0000 Message-ID: <179181904740.2527009.16307700795539761723@kernel.org> In-Reply-To: <20261012-stmmac-xdp-tx-pre-fixes-v1-0-05fd0c90f7e1@oss.qualcomm.com> References: <20261012-stmmac-xdp-tx-pre-fixes-v1-0-05fd0c90f7e1@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.