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 442A9CA9ED1 for ; Mon, 12 Oct 2026 16:51:05 +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=Dwj6mokjwGBiiIIVXaUjmOS0WS Jb0VrwMD9kdjKpFBgYomduT8Iw/fCi1vWt4FTVD3ND9rxVAdNnGpizXekTKzhWBB/ZTY3wOwopoaU ilHs0BCJ35wxGO06eFIxFqg2OQXN26PHCFxWptVoW6e5LQFnXY2Hmkro3wEF4LkCjQaq8Kk57NEVy Z3jXHeF9mgpdc+dH5ZVOpoyjnpCFW4k+rNV2WeBa2QFHlWm/zGwW2OmnzZPz8xr/jewIGNHzL9L2N 3Wb4BtOapVa83FXhjlZferFwPmNYT3YhbspEs613G9eS6DNw0LBjEJD7dc8wWdT8WZ+Gcs83V1eoP xQV2c+VA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xGJEl-0000000B1Mm-0x8R; Mon, 12 Oct 2026 16:50:55 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1xGJEk-0000000B1Mf-10Xi for linux-arm-kernel@lists.infradead.org; Mon, 12 Oct 2026 16:50:54 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id BF34743445; Mon, 12 Oct 2026 16:50:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id AA6481F0089B; Mon, 12 Oct 2026 16:50:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791823851; bh=URC7r36kokGjXCV5G6Ei8oKV54JoMbconYpCKkPt2AY=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=nQ1Ha96IJ566DWSumPsm1fyyjKEDtuXzozQ1iJe7SbD1KDMygCf4W1woZIHznWIjO mJC54gMuDBlxFQZ+uDbv/XbuDfOoZunVXfPoNQei0A+nRXncJCbaaO4s9dmIK11zp1 PxpGrunoEh0Nt4mQ3ENx7K1aYEVjLX5VSw+4KwBPUJfuNW10cY9jZpKUkduSAF5frd 9z4zqRI1NWXHUhMlpeEvu9CpS6hX76Cw9ERdb7tg+6vMRwYg/eLPdfgTxcEAD8fkia UZC70MBEnc48sL9wfxZUH7ftANv/qCwOnwdQxhbrIQnNY34XgCdSQq3epqNQnFlzRB wu10JHFkTvT9Q== 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 Subject: Re: [PATCH net-next v6 0/4] net: stmmac: introduce XDP rx multi-buff support Date: Mon, 12 Oct 2026 16:50:50 +0000 Message-ID: <179182385023.2527009.17648648661045341604@kernel.org> In-Reply-To: <20261012-stmmac-rx-mb-v6-0-2225050915c1@oss.qualcomm.com> References: <20261012-stmmac-rx-mb-v6-0-2225050915c1@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.