From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: [PATCH 0/2] irq: Cleanups in irq_exit()
Date: Fri, 22 Feb 2013 02:36:09 +0100 [thread overview]
Message-ID: <1361496971-16939-1-git-send-email-fweisbec@gmail.com> (raw)
Hi,
Those are based on tip:/irq/urgent. I'm pretty confident about the
1st patch. The 2nd patch passed through some discussions with Thomas:
it's a nice cleanup but it involves a small unfortunate workaround,
so I tagged it as an RFC. I have mixed feelings about it.
Thanks.
Frederic Weisbecker (2):
irq: Remove IRQ_EXIT_OFFSET workaround
irq: Cleanup context state transitions in irq_exit()
include/linux/hardirq.h | 3 +-
kernel/softirq.c | 53 +++++++++++++++++++++++++++++++++++++++--------
2 files changed, 45 insertions(+), 11 deletions(-)
--
1.7.5.4
next reply other threads:[~2013-02-22 1:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 1:36 Frederic Weisbecker [this message]
2013-02-22 1:36 ` [PATCH 1/2] irq: Remove IRQ_EXIT_OFFSET workaround Frederic Weisbecker
2013-02-22 1:36 ` [PATCH 2/2] irq: Cleanup context state transitions in irq_exit() Frederic Weisbecker
2013-02-22 14:33 ` Thomas Gleixner
2013-02-22 15:04 ` Frederic Weisbecker
2013-02-22 15:06 ` Thomas Gleixner
2013-02-22 21:08 ` Linus Torvalds
2013-02-23 18:21 ` Frederic Weisbecker
2013-02-23 19:24 ` Linus Torvalds
2013-02-26 12:15 ` Thomas Gleixner
2013-02-26 14:28 ` Frederic Weisbecker
2013-02-26 15:14 ` Thomas Gleixner
2013-02-26 16:27 ` Frederic Weisbecker
2013-02-26 16:39 ` Paul E. McKenney
2013-02-26 18:55 ` Thomas Gleixner
2013-02-26 19:17 ` Paul E. McKenney
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=1361496971-16939-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).