From: Frederic Weisbecker <frederic@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [RFC PATCH 0/3] lockdep/irq: wait-type related cleanups
Date: Mon, 23 Mar 2020 04:32:04 +0100 [thread overview]
Message-ID: <20200323033207.32370-1-frederic@kernel.org> (raw)
Hi,
Here are a few cleanups after reviewing the wait-type related changes.
It's RFC since I might not have guessed correctly all your aims.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
locking/core
HEAD: 2324f8c6891a858aa1c61933489ebc266282e67f
Thanks,
Frederic
---
Frederic Weisbecker (3):
lockdep/irq: Be more strict about IRQ-threadable code end
lockdep: Merge hardirq_threaded and irq_config together
lockdep: Briefly comment current->hardirq_threadable usecases
include/linux/irqflags.h | 80 +++++++++++++++++++-----------------------
include/linux/sched.h | 3 +-
kernel/irq/handle.c | 12 +++++--
kernel/locking/lockdep.c | 2 +-
kernel/time/posix-cpu-timers.c | 7 ++--
kernel/time/tick-sched.c | 4 +++
6 files changed, 56 insertions(+), 52 deletions(-)
next reply other threads:[~2020-03-23 3:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 3:32 Frederic Weisbecker [this message]
2020-03-23 3:32 ` [RFC PATCH 1/3] lockdep/irq: Be more strict about IRQ-threadable code end Frederic Weisbecker
2020-03-23 13:53 ` Peter Zijlstra
2020-03-23 15:30 ` Frederic Weisbecker
2020-03-23 16:31 ` Peter Zijlstra
2020-03-24 3:20 ` Frederic Weisbecker
2020-03-23 3:32 ` [RFC PATCH 2/3] lockdep: Merge hardirq_threaded and irq_config together Frederic Weisbecker
2020-03-23 14:02 ` Peter Zijlstra
2020-03-23 14:53 ` Sebastian Andrzej Siewior
2020-03-23 16:14 ` Frederic Weisbecker
2020-03-23 3:32 ` [RFC PATCH 3/3] lockdep: Briefly comment current->hardirq_threadable usecases Frederic Weisbecker
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=20200323033207.32370-1-frederic@kernel.org \
--to=frederic@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.