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 55766CA6019 for ; Fri, 9 Oct 2026 10:30:34 +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=vO1vYg7tOZ8soEd5Xc1Itb7REC ksQoQeZ277VVJ9DKlv8sRkK4RXACb/eGnv7Vt8ZDz1VM6d0Tfg2ysD0q0HLys01oRGpx0idm34Mdk qcXhCNH07212D4Rwz56PXz9WYvtWl/dD1ekd4TEzhpliyvy8d7Lrr5/Pa+qQ7c4hJ4tg4jIqp+rw3 uUz74Ko7Ukz0oQFaB2a0aifGW3zyY2wEKTrUgzNH9ar2GP1YXkF59JRKpv/U+x+QHj5hYOQhGOIQV B0oQRqs+86gGmcoed9Q9jVQG46jW4FsC4ANJaz88Bqjtcl7e5ZHDvjcGWSFgCr+WTtK0hGPmc8RJ7 PJWGqP8A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xF7rv-000000064DD-3lFN; Fri, 09 Oct 2026 10:30:27 +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 1xF7ru-000000064C6-12l1 for linux-arm-kernel@lists.infradead.org; Fri, 09 Oct 2026 10:30:26 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 760296053A; Fri, 9 Oct 2026 10:30:25 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 23CB71F000FF; Fri, 9 Oct 2026 10:30:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791541825; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=DJVRWBF//LTZ9A+Pw0aZTVccxYUuh3vpa/X0StCzB3z/L0c8lzEzWvgpK9SOoS4k9 FrX4U8ErewvwMYftLDk2pdQADpDrB/nfgEUAF4uIB6rXLU44ifNwVIT0tLRRegRJkF rSCqc096EJ1a/iaHcEBrg8mI6PUMn3UnJkUms68jyxfNIgzQb5UkRwd7ebaT1zMOsr xg4iZ3ZAXCkp3IeoWWc3/Rn4uIrLssdjZ08SZE5gTpZFp7RPOAyt1pUB1Bmoaa64bm 7yLgyCbBv+DQW9x2FZkwr64VYEuTTHm+AdulHtZQWYiTIORIoNjspoa+OF22aDyI4e 4mRmRxuAtyDnA== 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 , Jose Abreu , Ong Boon Leong , netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, bpf@vger.kernel.org, James Hilliard Subject: Re: [PATCH net-next v5 0/3] net: stmmac: introduce XDP rx multi-buff support Date: Fri, 09 Oct 2026 10:30:23 +0000 Message-ID: <179154182368.2527009.383686573505818394@kernel.org> In-Reply-To: <20261009-stmmac-rx-mb-v5-0-c38fa4eaa138@oss.qualcomm.com> References: <20261009-stmmac-rx-mb-v5-0-c38fa4eaa138@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.