public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Frederic Weisbecker <frederic@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Wei Li <liwei391@huawei.com>,
	Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>,
	Yu Liao <liaoyu15@huawei.com>, Hillf Danton <hdanton@sina.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 0/6] timers/nohz: Fixes and cleanups
Date: Mon, 13 Feb 2023 19:36:39 +0100	[thread overview]
Message-ID: <87fsb9tnt4.ffs@tglx> (raw)
In-Reply-To: <20230210140917.279062-1-frederic@kernel.org>

On Fri, Feb 10 2023 at 15:09, Frederic Weisbecker wrote:
> Try to (partially) fix the issue reported in https://lore.kernel.org/lkml/20230128020051.2328465-1-liaoyu15@huawei.com/

Looks about right. Can you please remove that assert in the selftest
which started all this?

Thanks,

        tglx

      parent reply	other threads:[~2023-02-13 18:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 14:09 [PATCH 0/6] timers/nohz: Fixes and cleanups Frederic Weisbecker
2023-02-10 14:09 ` [PATCH 1/6] timers/nohz: Restructure and reshuffle struct tick_sched Frederic Weisbecker
2023-02-10 14:09 ` [PATCH 2/6] timers/nohz: Only ever update sleeptime from idle exit Frederic Weisbecker
2023-02-10 14:09 ` [PATCH 3/6] timers/nohz: Protect idle/iowait sleep time under seqcount Frederic Weisbecker
2023-02-10 14:09 ` [PATCH 4/6] timers/nohz: Add a comment about broken iowait counter update race Frederic Weisbecker
2023-02-10 14:39   ` Peter Zijlstra
2023-02-10 16:10     ` Frederic Weisbecker
2023-02-10 14:09 ` [PATCH 5/6] timers/nohz: Remove middle-function __tick_nohz_idle_stop_tick() Frederic Weisbecker
2023-02-10 14:09 ` [PATCH 6/6] MAINTAINERS: Remove stale email address Frederic Weisbecker
2023-02-10 14:41 ` [PATCH 0/6] timers/nohz: Fixes and cleanups Peter Zijlstra
2023-02-13 18:36 ` Thomas Gleixner [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=87fsb9tnt4.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=adobriyan@gmail.com \
    --cc=frederic@kernel.org \
    --cc=hdanton@sina.com \
    --cc=liaoyu15@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liwei391@huawei.com \
    --cc=mingo@kernel.org \
    --cc=mirsad.todorovac@alu.unizg.hr \
    --cc=peterz@infradead.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