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 9172ECC6B1A for ; Wed, 14 Oct 2026 13:16: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=v832a42Tz9IqsRryi3REJXxaM1 FgWjZbR8sZ5FfKbR+ooO+Bs/1WkSGQoH794rb71jA2MS4r2pBc0A23USQABhGYkoSRvg+8ADPo83w LVHPtDS0iF32j+5oSeH12lhmYHDE8NuRK6lX0h7xEc/xXVShPB2h2GLve6iN3K+p0cdjIgmhrtddw hoE0DFSRiNb/auD2ytu8/Gs8/Ba/RkOhpcjuPxt5MzhoOETMo3z7O5P34tNY8rsjPuQ7D9hLFTbRA HrhmM+jB/Lo2V7wFqrahCKmFMlEzB0nT9ssjSh49e7kOfnsb/LrrLJQMgI1LHWQJdAiz+Ph1sOn5g ZutJVdLw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xGypj-0000000FYUF-40PD; Wed, 14 Oct 2026 13:15:51 +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 1xGypi-0000000FYTp-3l3O for linux-arm-kernel@lists.infradead.org; Wed, 14 Oct 2026 13:15:50 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 404E360219; Wed, 14 Oct 2026 13:15:50 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C97221F000FF; Wed, 14 Oct 2026 13:15:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791983750; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=bI3Vs5g2cTAt0pA+fCkxvmCVcJ3EDcyeVDFZNUshQAfs40TWr5WVp6TMdoYuTmQD+ bYHutaEsJpojwyCWp+PNjtFkUC2P9zEOYNX9/WTaa/BOWocm2dQKnyiKLYR4YHTMwO sBiOPFUX7JDGCqlbBgK6vEhKr5Z5z1aKg+/JeckHY+jy9+W6xv8I4P2zG0RjgQjR1o 0rWnzSV/9XWsVO56U8Lb0c9VhUeqcJpA+qpcRgYrNMjlx5QrAMcXM3Bxv/fp7P5aBI sKK3rpyaX2EynVotIeXFGrWAog6ETAPoJ+TvfDTN7+UYka02EM0HSwR3gdDMGAPW0R WAof7Spo5NmCQ== 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-arm-kernel@lists.infradead.org, bpf@vger.kernel.org, James Hilliard , Nicolai Buchwitz Subject: Re: [PATCH net-next v7 0/4] net: stmmac: introduce XDP rx multi-buff support Date: Wed, 14 Oct 2026 13:15:48 +0000 Message-ID: <179198374828.320699.17103999780938670424@kernel.org> In-Reply-To: <20261014-stmmac-rx-mb-v7-0-5d2d70f052cd@oss.qualcomm.com> References: <20261014-stmmac-rx-mb-v7-0-5d2d70f052cd@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.