From: Richard Weinberger <richard@nod.at>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: user-mode-linux-devel@lists.sourceforge.net,
peterz@infradead.org, jdike@addtoit.com,
linux-kernel@vger.kernel.org,
user-mode-linux-user@lists.sourceforge.net, tj@kernel.org,
tglx@linutronix.de, mingo@elte.hu
Subject: Re: [uml-devel] [PATCH 1/1] um: Get rid of __do_IRQ()
Date: Tue, 12 Oct 2010 00:23:10 +0200 [thread overview]
Message-ID: <201010120023.10861.richard@nod.at> (raw)
In-Reply-To: <20101011151447.1a022f25.akpm@linux-foundation.org>
Am Dienstag 12 Oktober 2010, 00:14:47 schrieb Andrew Morton:
> What's the plan here? Are all architectures supposed to me migrating
> away from __do_IRQ() and over to generic_handle_irq(), or what?
Yes.
Documentation/feature-removal-schedule.txt:
What: __do_IRQ all in one fits nothing interrupt handler
When: 2.6.32
Why: __do_IRQ was kept for easy migration to the type flow handlers.
More than two years of migration time is enough.
Who: Thomas Gleixner <tglx@linutronix.de>
Thanks,
//richard
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2010-10-11 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 21:29 [PATCH 1/1] um: Get rid of __do_IRQ() Richard Weinberger
2010-10-11 22:14 ` [uml-devel] " Andrew Morton
2010-10-11 22:23 ` Richard Weinberger [this message]
2010-10-11 22:29 ` Thomas Gleixner
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=201010120023.10861.richard@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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