From: David Miller <davem@davemloft.net>
To: alistair@popple.id.au
Cc: netdev@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: [PATCH 2/2] ibm emac: Fix locking for enable/disable eob irq
Date: Tue, 29 Oct 2013 22:58:27 -0400 (EDT) [thread overview]
Message-ID: <20131029.225827.1459363885174411483.davem@davemloft.net> (raw)
In-Reply-To: <1383090638-21526-2-git-send-email-alistair@popple.id.au>
From: Alistair Popple <alistair@popple.id.au>
Date: Wed, 30 Oct 2013 10:50:38 +1100
> Calls to mal_enable_eob_irq perform a read-write-modify of a dcr to
> enable device irqs which is protected by a spin lock. However calls to
> mal_disable_eob_irq do not take the corresponding lock.
>
> This patch resolves the problem by ensuring that calls to
> mal_disable_eob_irq also take the lock.
>
> Signed-off-by: Alistair Popple <alistair@popple.id.au>
Applied.
next prev parent reply other threads:[~2013-10-30 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 23:50 [PATCH 1/2] ibm emac: Don't call napi_complete if napi_reschedule failed Alistair Popple
2013-10-29 23:50 ` [PATCH 2/2] ibm emac: Fix locking for enable/disable eob irq Alistair Popple
2013-10-30 2:58 ` David Miller [this message]
2013-10-30 2:58 ` [PATCH 1/2] ibm emac: Don't call napi_complete if napi_reschedule failed 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=20131029.225827.1459363885174411483.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--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).