From: Peter Zijlstra <peterz@infradead.org>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: linux-kernel@vger.kernel.org, cai@gmx.us,
daniel.lezcano@linaro.org, linux-arm-kernel@lists.infradead.org,
longman@redhat.com, marc.zyngier@arm.com, mark.rutland@arm.com,
mingo@kernel.org, tglx@linutronix.de, dietmar.eggemann@arm.com
Subject: Re: [PATCH 0/2] System-wide mute of hotplug lockdep during init
Date: Fri, 11 Jan 2019 14:01:30 +0100 [thread overview]
Message-ID: <20190111130130.GA12917@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <0f2b6cc8-ad2f-bd0b-fe51-c333a8033452@arm.com>
On Fri, Jan 11, 2019 at 09:53:58AM +0000, Valentin Schneider wrote:
> Hi,
>
> On 19/12/2018 18:23, Valentin Schneider wrote:
> > In [1] Peter had a suggestion to broadly mute hotplug lockdep warnings during
> > init instead of going after every single warning and wrapping them with
> > cpus_read_{lock, unlock}(). This is implemented in [PATCH 1/2].
> >
> > [PATCH 2/2] is a logical follow-up as [PATCH 1/2] is the generalized version
> > of the reverted patch.
> >
> > [1]: https://lore.kernel.org/lkml/1543877121-4098-1-git-send-email-cai@gmx.us/#t
> >
>
> Gentle ping - I suppose this flew under the holidays radar.
Indeed so... got them now. Thanks!
prev parent reply other threads:[~2019-01-11 13:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 18:23 [PATCH 0/2] System-wide mute of hotplug lockdep during init Valentin Schneider
2018-12-19 18:23 ` [PATCH 1/2] cpu/hotplug: Mute " Valentin Schneider
2018-12-19 18:31 ` Marc Zyngier
2019-01-21 11:30 ` [tip:locking/core] " tip-bot for Valentin Schneider
2018-12-19 18:23 ` [PATCH 2/2] Revert "sched/core: Take the hotplug lock in sched_init_smp()" Valentin Schneider
2019-01-21 11:30 ` [tip:locking/core] " tip-bot for Valentin Schneider
2019-01-11 9:53 ` [PATCH 0/2] System-wide mute of hotplug lockdep during init Valentin Schneider
2019-01-11 13:01 ` Peter Zijlstra [this message]
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=20190111130130.GA12917@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cai@gmx.us \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.com \
/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).