From: Greg KH <gregkh@linuxfoundation.org>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: linux-wireless@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: vt6655: Fix Warning on boot handle_irq_event_percpu.
Date: Wed, 23 Jul 2014 16:12:00 -0700 [thread overview]
Message-ID: <20140723231200.GB31075@kroah.com> (raw)
In-Reply-To: <1406147712-3152-1-git-send-email-tvboxspy@gmail.com>
On Wed, Jul 23, 2014 at 09:35:11PM +0100, Malcolm Priestley wrote:
> WARNING: CPU: 0 PID: 929 at /home/apw/COD/linux/kernel/irq/handle.c:147 handle_irq_event_percpu+0x1d1/0x1e0()
> irq 17 handler device_intr+0x0/0xa80 [vt6655_stage] enabled interrupts
>
> Using spin_lock_irqsave appears to fix this.
>
> Signed-off-by: Malcolm Priestley <tvboxspy@gmail.com>
> Cc: <stable@vger.kernel.org>
So should both of these go into the 3.16-final kernel release?
thanks,
greg k-h
next prev parent reply other threads:[~2014-07-23 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 20:35 [PATCH 1/2] staging: vt6655: Fix Warning on boot handle_irq_event_percpu Malcolm Priestley
2014-07-23 20:35 ` [PATCH 2/2] staging: vt6655: Fix disassociated messages every 10 seconds Malcolm Priestley
2014-07-23 23:12 ` Greg KH [this message]
2014-07-24 14:55 ` [PATCH 1/2] staging: vt6655: Fix Warning on boot handle_irq_event_percpu Malcolm Priestley
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=20140723231200.GB31075@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tvboxspy@gmail.com \
/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).