From: David Miller <davem@davemloft.net>
To: john@phrozen.org
Cc: nbd@nbd.name, keyhaede@gmail.com, netdev@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] net-next: mediatek: IRQ cleanups, fixes and grouping
Date: Wed, 15 Jun 2016 22:20:50 -0700 (PDT) [thread overview]
Message-ID: <20160615.222050.2210130284846212716.davem@davemloft.net> (raw)
In-Reply-To: <1466002730-58476-1-git-send-email-john@phrozen.org>
From: John Crispin <john@phrozen.org>
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.
next prev parent reply other threads:[~2016-06-16 5:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 14:58 [PATCH 0/4] net-next: mediatek: IRQ cleanups, fixes and grouping John Crispin
2016-06-15 14:58 ` [PATCH 1/4] net-next: mediatek: remove superfluous register reads John Crispin
2016-06-15 14:58 ` [PATCH 2/4] net-next: mediatek: don't use intermediate variables to store IRQ masks John Crispin
2016-06-15 14:58 ` [PATCH 3/4] net-next: mediatek: add IRQ locking John Crispin
2016-06-15 14:58 ` [PATCH 4/4] net-next: mediatek: add support for IRQ grouping John Crispin
2016-06-16 5:20 ` David Miller [this message]
2016-06-16 9:44 ` [PATCH 0/4] net-next: mediatek: IRQ cleanups, fixes and grouping John Crispin
2016-06-16 9:51 ` Daniel Borkmann
2016-06-17 0:27 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160615.222050.2210130284846212716.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=john@phrozen.org \
--cc=keyhaede@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).