From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754063AbcFPJvo (ORCPT ); Thu, 16 Jun 2016 05:51:44 -0400 Received: from www62.your-server.de ([213.133.104.62]:44433 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752217AbcFPJvm (ORCPT ); Thu, 16 Jun 2016 05:51:42 -0400 Message-ID: <576276A6.6040904@iogearbox.net> Date: Thu, 16 Jun 2016 11:51:34 +0200 From: Daniel Borkmann User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: John Crispin , David Miller 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 References: <1466002730-58476-1-git-send-email-john@phrozen.org> <20160615.222050.2210130284846212716.davem@davemloft.net> <5dbb935d-2d9a-48fe-79c7-8e8f57b27678@phrozen.org> In-Reply-To: <5dbb935d-2d9a-48fe-79c7-8e8f57b27678@phrozen.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: daniel@iogearbox.net Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/16/2016 11:44 AM, John Crispin wrote: > 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). if i resend this at the start of the next rc1 > would you merge it into the net tree so that it becomes part of v4.8 ? Well, it would rather require a merge of -net into -net-next then. But that would be useful indeed. Cheers, Daniel