From: Alexander Gordeev <agordeev@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Alexander Gordeev <agordeev@redhat.com>,
Tejun Heo <tj@kernel.org>, David Milburn <dmilburn@redhat.com>,
linux-ide@vger.kernel.org
Subject: [PATCH 0/1] ahci: Do not receive interrupts sent by dummy ports
Date: Thu, 17 Apr 2014 18:06:14 +0200 [thread overview]
Message-ID: <cover.1397750166.git.agordeev@redhat.com> (raw)
Tejun, David,
I would expect handle_bad_irq()->print_irq_desc() gets called
if dummy port interrupt arrived. Could be a spurious interrupt
complain as well.
Cc: Tejun Heo <tj@kernel.org>
Cc: David Milburn <dmilburn@redhat.com>
Cc: linux-ide@vger.kernel.org
Alexander Gordeev (1):
ahci: Do not receive interrupts sent by dummy ports
drivers/ata/ahci.c | 16 ++++++++++------
1 files changed, 10 insertions(+), 6 deletions(-)
--
1.7.7.6
next reply other threads:[~2014-04-17 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 16:06 Alexander Gordeev [this message]
2014-04-17 16:06 ` [PATCH 1/1] ahci: Do not receive interrupts sent by dummy ports Alexander Gordeev
2014-04-17 17:06 ` Tejun Heo
2014-04-17 17:50 ` David Milburn
2014-04-18 19:56 ` Tejun Heo
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=cover.1397750166.git.agordeev@redhat.com \
--to=agordeev@redhat.com \
--cc=dmilburn@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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).