From: Tejun Heo <tj@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/6] workqueue: convert to raw_spinlock_t
Date: Wed, 26 Jun 2019 07:18:19 -0700 [thread overview]
Message-ID: <20190626141819.GV657710@devbig004.ftw2.facebook.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1906261608260.32342@nanos.tec.linutronix.de>
Hello,
On Wed, Jun 26, 2019 at 04:12:15PM +0200, Thomas Gleixner wrote:
> We are working hard to get the remaining pieces in and to the best of my
> knowledge there is no hard resistance against merging them.
I wonder whether it'd be useful to build some consensus around the
approach. It'd be a lot easier for everyone involved than having the
same conversation repeatedly. What do you think?
> What we are trying at the moment is to reduce the surface of the bulk of RT
> changes and get the 'innocent' ones in. If you feel more comfortable, then
> we can surely redo the series and pick 1,2,6 for now and keep 3-5 for the
> final submission.
Yeah, that sounds good.
Thanks.
--
tejun
next prev parent reply other threads:[~2019-06-26 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 14:50 [PATCH 0/6] workqueue: convert to raw_spinlock_t Sebastian Andrzej Siewior
2019-06-13 14:50 ` [PATCH 1/6] workqueue: Make alloc/apply/free_workqueue_attrs() static Sebastian Andrzej Siewior
2019-06-13 14:50 ` [PATCH 2/6] workqueue: Remove GPF argument from alloc_workqueue_attrs() Sebastian Andrzej Siewior
2019-06-13 14:50 ` [PATCH 3/6] workqueue: Don't assume that the callback has interrupts disabled Sebastian Andrzej Siewior
2019-06-13 14:50 ` [PATCH 4/6] sched/swait: Add swait_event_lock_irq() Sebastian Andrzej Siewior
2019-06-13 14:50 ` [PATCH 5/6] workqueue: Use swait for wq_manager_wait Sebastian Andrzej Siewior
2019-06-13 14:50 ` [PATCH 6/6] workqueue: Convert the locks to raw type Sebastian Andrzej Siewior
2019-06-26 7:17 ` [PATCH 0/6] workqueue: convert to raw_spinlock_t Sebastian Andrzej Siewior
2019-06-26 13:49 ` Tejun Heo
2019-06-26 13:53 ` Thomas Gleixner
2019-06-26 14:01 ` Tejun Heo
2019-06-26 14:12 ` Thomas Gleixner
2019-06-26 14:18 ` Tejun Heo [this message]
2019-06-26 14:09 ` Sebastian Andrzej Siewior
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=20190626141819.GV657710@devbig004.ftw2.facebook.com \
--to=tj@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox