From: Arnd Bergmann <arnd@arndb.de>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
rpao@paonet.org, linux-kernel@vger.kernel.org,
linux-pcmcia@lists.infradead.org
Subject: Re: [PATCH 1/2] net/am2150: fix nmclan_cs.c shared interrupt handling
Date: Mon, 24 Nov 2014 11:57:55 +0100 [thread overview]
Message-ID: <2416727.91yS5gqAdt@wuerfel> (raw)
In-Reply-To: <20141121.151735.1432199551923486515.davem@davemloft.net>
On Friday 21 November 2014 15:17:35 David Miller wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> Date: Thu, 20 Nov 2014 16:11:14 +0100
>
> > A recent patch tried to work around a valid warning for the use of a
> > deprecated interface by blindly changing from the old
> > pcmcia_request_exclusive_irq() interface to pcmcia_request_irq().
> >
> > This driver has an interrupt handler that is not currently aware
> > of shared interrupts, but can be easily converted to be.
> > At the moment, the driver reads the interrupt status register
> > repeatedly until it contains only zeroes in the interesting bits,
> > and handles each bit individually.
> >
> > This patch adds the missing part of returning IRQ_NONE in case none
> > of the bits are set to start with, so we can move on to the next
> > interrupt source.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > Fixes: 5f5316fcd08ef7 ("am2150: Update nmclan_cs.c to use update PCMCIA API")
> > ---
> > I had this patch in my queue of things to submit and noticed that
> > the warning had gone away upstream but my patch was still there.
> >
> > For all I can tell, the driver is broken without this, although it
> > would rarely be a problem.
>
> I'm happy for this to go alongside patch #2 via another tree:
>
> Acked-by: David S. Miller <davem@davemloft.net>
I was hoping you could take at least this one, possibly both.
Since you already had Jeff's patch in it, the first patch now
fixes a (mostly harmless) 3.18 regression, and the second patch
is just a cosmetic cleanup, but there is no longer any dependency
between the two.
It looks like Greg is now handling most of the PCMCIA patches
in the absence of a subsystem maintainer, so I'll send him the
second one for 3.19, let me know if you still want me to send
him the first one too.
Arnd
prev parent reply other threads:[~2014-11-24 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 15:11 [PATCH 1/2] net/am2150: fix nmclan_cs.c shared interrupt handling Arnd Bergmann
2014-11-20 15:21 ` [PATCH 2/2] pcmcia: remove pcmcia_request_exclusive_irq Arnd Bergmann
2014-11-21 20:17 ` [PATCH 1/2] net/am2150: fix nmclan_cs.c shared interrupt handling David Miller
2014-11-24 10:57 ` Arnd Bergmann [this message]
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=2416727.91yS5gqAdt@wuerfel \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=rpao@paonet.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).