From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Subject: How to get rid of IRQF_DISABLED for good?
Date: Thu, 20 Feb 2014 18:44:41 +0100 [thread overview]
Message-ID: <53063F09.9000102@free-electrons.com> (raw)
Hi,
In spite of the patches I have been sending (and resending!) over the
past months, there are still 118 occurrences of the idle IRQF_DISABLED
flag in the kernel code. This corresponds to 31 patches which haven't
been accepted yet.
What would you advise to get rid of IRQF_DISABLED for good?
* Send a treewide patch removing the last occurrences in one shot,
bypassing the regular maintainers? Who could take it?
* Remove the definition of IRQF_DISABLED to force the individual
maintainers (and out of tree drivers!) to update their code? It
could be a way of seeing which code isn't maintained any more ;)
* Continue to resend the patches for a few more cycles, until the
corresponding maintainers can no longer bear the discredit?
* Any other solution?
Thank you in advance for your advise!
Michael.
--
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098
next reply other threads:[~2014-02-20 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 17:44 Michael Opdenacker [this message]
2014-02-20 18:17 ` How to get rid of IRQF_DISABLED for good? Levente Kurusa
2014-03-05 6:01 ` Michael Opdenacker
2014-03-06 20:43 ` Geert Uytterhoeven
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=53063F09.9000102@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.