From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754574AbcFQA13 (ORCPT ); Thu, 16 Jun 2016 20:27:29 -0400 Received: from shards.monkeyblade.net ([149.20.54.216]:44574 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753818AbcFQA11 (ORCPT ); Thu, 16 Jun 2016 20:27:27 -0400 Date: Thu, 16 Jun 2016 17:27:26 -0700 (PDT) Message-Id: <20160616.172726.2001945071088559824.davem@davemloft.net> To: john@phrozen.org Cc: netdev@vger.kernel.org, linux-mediatek@lists.infradead.org, keyhaede@gmail.com, linux-kernel@vger.kernel.org, nbd@nbd.name Subject: Re: [PATCH 0/4] net-next: mediatek: IRQ cleanups, fixes and grouping From: David Miller In-Reply-To: <5dbb935d-2d9a-48fe-79c7-8e8f57b27678@phrozen.org> References: <1466002730-58476-1-git-send-email-john@phrozen.org> <20160615.222050.2210130284846212716.davem@davemloft.net> <5dbb935d-2d9a-48fe-79c7-8e8f57b27678@phrozen.org> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 16 Jun 2016 17:27:26 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: John Crispin Date: Thu, 16 Jun 2016 11:44:44 +0200 > > > On 16/06/2016 07:20, David Miller wrote: >> From: John Crispin >> Date: Wed, 15 Jun 2016 16:58:46 +0200 >> >>> This series contains 2 small code cleanups that are leftovers from the >>> MIPS support. There is also a small fix that adds proper locking to the >>> code accessing the IRQ registers. Without this fix we saw deadlocks caused >>> by the last patch of the series, which adds IRQ grouping. The grouping >>> feature allows us to use different IRQs for TX and RX. By doing so we can >>> use affinity to let the SoC handle the IRQs on different cores. >> >> This patch series doesn't apply cleanly to the net-next tree, I get rejects >> on patch #4. >> > > it depends on the series with the 11 fixes that i sent last week which > is however in the net tree and not the next tree (i also still had the > DQL hack in my tree). Then you need to tell me about such dependencies in your submission.