From: xiubli@redhat.com
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Cc: hamish.martin@alliedtelesis.co.nz, jannh@google.com,
pkalever@redhat.com, pkarampu@redhat.com, atumball@redhat.com,
sabose@redhat.com, mchristi@redhat.com
Subject: [PATCH v3 1/3] uio: use request_threaded_irq instead
Date: Thu, 5 Jul 2018 22:57:14 -0400 [thread overview]
Message-ID: <1530845836-49101-2-git-send-email-xiubli@redhat.com> (raw)
In-Reply-To: <1530845836-49101-1-git-send-email-xiubli@redhat.com>
From: Xiubo Li <xiubli@redhat.com>
Prepraing for changing to use mutex lock.
Signed-off-by: Xiubo Li <xiubli@redhat.com>
---
drivers/uio/uio.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/uio/uio.c b/drivers/uio/uio.c
index e8f4ac9..b4b2ae1 100644
--- a/drivers/uio/uio.c
+++ b/drivers/uio/uio.c
@@ -902,8 +902,9 @@ int __uio_register_device(struct module *owner,
* FDs at the time of unregister and therefore may not be
* freed until they are released.
*/
- ret = request_irq(info->irq, uio_interrupt,
- info->irq_flags, info->name, idev);
+ ret = request_threaded_irq(info->irq, NULL, uio_interrupt,
+ info->irq_flags, info->name, idev);
+
if (ret)
goto err_request_irq;
}
--
1.8.3.1
next prev parent reply other threads:[~2018-07-06 2:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 2:57 [PATCH v3 0/3] uio: fix potential crash bug xiubli
2018-07-06 2:57 ` xiubli [this message]
2018-07-06 2:57 ` [PATCH v3 2/3] uio: change to use the mutex lock instead of the spin lock xiubli
2018-07-06 3:39 ` Hamish Martin
2018-07-06 2:57 ` [PATCH v3 3/3] uio: fix crash after the device is unregistered xiubli
2018-07-06 3:40 ` Hamish Martin
2018-07-06 18:23 ` Mike Christie
2018-07-07 1:28 ` Xiubo Li
2018-07-09 17:06 ` Mike Christie
2018-07-10 2:40 ` Xiubo Li
2018-07-06 18:58 ` Mike Christie
2018-07-07 1:47 ` Xiubo Li
2018-07-09 16:40 ` Mike Christie
2018-07-10 2:36 ` Xiubo Li
2018-07-06 3:31 ` [PATCH v3 0/3] uio: fix potential crash bug Hamish Martin
2018-07-06 12:04 ` Xiubo Li
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=1530845836-49101-2-git-send-email-xiubli@redhat.com \
--to=xiubli@redhat.com \
--cc=atumball@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hamish.martin@alliedtelesis.co.nz \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=pkalever@redhat.com \
--cc=pkarampu@redhat.com \
--cc=sabose@redhat.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
all inboxes | Powered by JetHome®