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 DD472CE7AB9 for ; Fri, 6 Sep 2024 07:12:53 +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:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=prFiJs2tRSrNRntjIb9KHWv5WFK9Mx21U33UtitUT6U=; b=EYR4YLwE3E0vsimibMswEJecc6 LY7gc4X4QC86/ro/rTBrOXp1ZO34aAxGvlDu50EvxHgxT4vKE3lv/RAeXrsPSFisAnu5NHGTcG2GK vmMr5PT3B6dGwajQhK8QQuHQMpskWwwvspu7N0I57jA/UQZWg+QAvVDJdI2uu9NC02VAEqDqT1tBv JCN/2BhthspuaBxP40jApcdfHYom+zaoYicjNleD8QitB8VGYgH4g2a5rMroVY8SaIBrHmN5gsWbo BmvxOIDHlNM/2t/WY+pBEazsuc9PCDXu6I3vChtDywTppxrA513w6FNgSWCua5/jjdI6NCRMGBGh4 ZIQ5yVhg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1smT9A-0000000B2SR-3Vrv; Fri, 06 Sep 2024 07:12:44 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1smT0R-0000000B01U-0NGH for linux-arm-kernel@lists.infradead.org; Fri, 06 Sep 2024 07:03:44 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 9245B5C3ED2; Fri, 6 Sep 2024 07:03:37 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 900ABC4CEC4; Fri, 6 Sep 2024 07:03:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1725606220; bh=XosyfNwJeFXOQHRLgM+l6NjMHrTnOYEKaf5JavecBl4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RImlA/LCGzIxQrv5on0OCtCoLNLx/B45N3EYOs+TSxZqcJteZxindT458nHNTnff9 LX+sY++09mpOpLReSItz4hujPrkjUxLAzF7Pq7OoxS1nQWeCX23dYH2g30msvL+esR LuEnSwVxmyM6QXIL0Isqsy9i3V2DpXgJbaP4Hz6pQYfUo29u/IKwwew3KXf1CD9eAu W0TJca3+CcuULOCkW8HkFq0cqJqbBbph567PFu+0VYEDXnrog93eplHSsQJvdNUbqN jfEBT9ADPOtD31MgpHJhGFIAayZYfiZZiCqyJe0TgDy4n8V0Q1KXLeBhn7K1KF4m1G eeHB9rbN69T8A== Date: Fri, 6 Sep 2024 08:03:36 +0100 From: Simon Horman To: Sean Anderson Cc: "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Radhey Shyam Pandey , netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Michal Simek , Heng Qi Subject: Re: [PATCH net-next 0/2] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM Message-ID: <20240906070336.GJ1722938@kernel.org> References: <20240903192524.4158713-1-sean.anderson@linux.dev> <20240904163503.GA1722938@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240906_000343_216054_EA22362D X-CRM114-Status: GOOD ( 22.76 ) 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 On Thu, Sep 05, 2024 at 10:27:00AM -0400, Sean Anderson wrote: > On 9/4/24 12:35, Simon Horman wrote: > > On Tue, Sep 03, 2024 at 03:25:22PM -0400, Sean Anderson wrote: > >> To improve performance without sacrificing latency under low load, > >> enable DIM. While I appreciate not having to write the library myself, I > >> do think there are many unusual aspects to DIM, as detailed in the last > >> patch. > >> > >> This series depends on [1]. > >> > >> [1] https://lore.kernel.org/netdev/20240903180059.4134461-1-sean.anderson@linux.dev/ > > > > Hi Sean, > > > > Unfortunately the CI doesn't understand dependencies, > > and so it is unable to apply this patchset :( > > > > I would suggest bundling patches for the same driver for net-next > > in a single patchset. And in any case, only having one active > > at any given time. > > > > Well, I would normally do so, but that patch is a fix and this series is > an improvement. So that one goes into net and this one goes into net-next. > > I've been advised in the past to split up independent patches so they can be > reviewed/applied individually. Thanks Sean, Understood. Given the first point, which I had missed earlier, I'd would have suggested marking this patch-set as an RFC, then reposting it once the dependency hits net-next (via net).