All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Jing-Ting Wu <jing-ting.wu@mediatek.com>
Cc: tglx@linutronix.de, valentin.schneider@arm.com,
	bristot@redhat.com, wsd_upstream@mediatek.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, Jonathan.JMChen@mediatek.com,
	Chris.Redpath@arm.com
Subject: Re: [Bug] Race condition between CPU hotplug off flow and __sched_setscheduler()
Date: Fri, 6 May 2022 09:47:44 +0200	[thread overview]
Message-ID: <20220506074744.GH2501@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <a34049745934652483e3958e0a030a45b6fcfb40.camel@mediatek.com>

On Fri, May 06, 2022 at 12:19:28PM +0800, Jing-Ting Wu wrote:
> Hi all
> Add Chris for status sync.

Please try another posting, that's eminently unreadable garbage due to
line wrapping.

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Jing-Ting Wu <jing-ting.wu@mediatek.com>
Cc: tglx@linutronix.de, valentin.schneider@arm.com,
	bristot@redhat.com, wsd_upstream@mediatek.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, Jonathan.JMChen@mediatek.com,
	Chris.Redpath@arm.com
Subject: Re: [Bug] Race condition between CPU hotplug off flow and __sched_setscheduler()
Date: Fri, 6 May 2022 09:47:44 +0200	[thread overview]
Message-ID: <20220506074744.GH2501@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <a34049745934652483e3958e0a030a45b6fcfb40.camel@mediatek.com>

On Fri, May 06, 2022 at 12:19:28PM +0800, Jing-Ting Wu wrote:
> Hi all
> Add Chris for status sync.

Please try another posting, that's eminently unreadable garbage due to
line wrapping.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Jing-Ting Wu <jing-ting.wu@mediatek.com>
Cc: tglx@linutronix.de, valentin.schneider@arm.com,
	bristot@redhat.com, wsd_upstream@mediatek.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, Jonathan.JMChen@mediatek.com,
	Chris.Redpath@arm.com
Subject: Re: [Bug] Race condition between CPU hotplug off flow and __sched_setscheduler()
Date: Fri, 6 May 2022 09:47:44 +0200	[thread overview]
Message-ID: <20220506074744.GH2501@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <a34049745934652483e3958e0a030a45b6fcfb40.camel@mediatek.com>

On Fri, May 06, 2022 at 12:19:28PM +0800, Jing-Ting Wu wrote:
> Hi all
> Add Chris for status sync.

Please try another posting, that's eminently unreadable garbage due to
line wrapping.

       reply	other threads:[~2022-05-06  7:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6013fb81cdb18892b75c796ab0e6756ee0e9cf71.camel@mediatek.com>
     [not found] ` <a34049745934652483e3958e0a030a45b6fcfb40.camel@mediatek.com>
2022-05-06  7:47   ` Peter Zijlstra [this message]
2022-05-06  7:47     ` [Bug] Race condition between CPU hotplug off flow and __sched_setscheduler() Peter Zijlstra
2022-05-06  7:47     ` Peter Zijlstra
2022-05-19 12:53 Jing-Ting Wu
2022-05-19 12:53 ` Jing-Ting Wu
2022-05-19 12:53 ` Jing-Ting Wu
2022-05-19 13:14 ` Peter Zijlstra
2022-05-19 13:14   ` Peter Zijlstra
2022-05-19 13:14   ` Peter Zijlstra
2022-05-19 13:19   ` Peter Zijlstra
2022-05-19 13:19     ` Peter Zijlstra
2022-05-19 13:19     ` Peter Zijlstra
2022-05-19 13:47 ` Peter Zijlstra
2022-05-19 13:47   ` Peter Zijlstra
2022-05-19 13:47   ` Peter Zijlstra

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=20220506074744.GH2501@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Chris.Redpath@arm.com \
    --cc=Jonathan.JMChen@mediatek.com \
    --cc=bristot@redhat.com \
    --cc=jing-ting.wu@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=tglx@linutronix.de \
    --cc=valentin.schneider@arm.com \
    --cc=wsd_upstream@mediatek.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 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.