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 4470CCCF2C4 for ; Sun, 18 Oct 2026 17:08:24 +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=nitqYCaU7x3I6O0iqsYbMQXcw2 ruBgmuTZZbPwDIiXWSfmqYJ9uzBStCw1eIT5qKwiWLPWImwrTXQxCpu8DrTx1LF0Une2bC8+Zktvs rhp9YuBF0iCQYHZRZuGf7GOZKo543Uq5Vw31mNaI/4kSuskGeLvn/PmS8DbGlip60AnadIQh0Fgzb o1Q/izUGHakfn2RV32sbQTxsMNlrxVsfIdGppZgDzPPknaEpoFFY4RcvghZrH3BkgZgm8N6ZnlAZY F9pNUjGTPkCBFjQrTDBBCk9eE7lXlh+4s5WCNhL9gO0QxiVCH0LOge2XmJp/PNrEkxtsovxLPXpjd nuLRg3Mg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xIUMr-000000064ti-23p9; Sun, 18 Oct 2026 17:08:17 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xIUMo-000000064rx-1wBW for linux-arm-kernel@lists.infradead.org; Sun, 18 Oct 2026 17:08:15 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 98B4A600D1; Sun, 18 Oct 2026 17:08:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4C38D1F000C4; Sun, 18 Oct 2026 17:08:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1792343293; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=NlbIYCJeSiHmKgJtDxLjfnn2vYxKh8Bw0KVVXzmCjP270pnYmi91kb6mAmLk26GGj W1zyyJnHBmwmyLvMhpPeB4xvRbctFPNBxWvqhcvZ7QlmxMYLwwNlU/if8EJjhTLbip k2MfCZggstZ77jpojfOEs9XYSs+17ExX3QdC33+aT7EkHeDF3KRvxAt+76J5qCUv7h QbIevnGxaZdEff3QM121Sd6+uCyuC9ChHceOxsqYkGKYcIIYCPh0ksqasLW8DBxrua n51O5Ssk8mIvX439sipsoWrXI/getdCWjXxuyUChmRYGJhLRRMxkOc37x93Rd4h/L/ nvW0N84Ye2ECg== 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 v8 0/5] net: stmmac: introduce XDP rx multi-buff support Date: Sun, 18 Oct 2026 17:08:11 +0000 Message-ID: <179234329183.3290.15960565045054355734@kernel.org> In-Reply-To: <20261018-stmmac-rx-mb-v8-0-5f58c0b25849@oss.qualcomm.com> References: <20261018-stmmac-rx-mb-v8-0-5f58c0b25849@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.