All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Cheng-Jui Wang <cheng-jui.wang@mediatek.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 00/10] Backport patches to fix lockdep splat in 6.1
Date: Fri, 10 Mar 2023 11:12:39 +0100	[thread overview]
Message-ID: <ZAsClzHcFVs+Hztr@kroah.com> (raw)
In-Reply-To: <20230303092347.4825-1-cheng-jui.wang@mediatek.com>

On Fri, Mar 03, 2023 at 05:23:22PM +0800, Cheng-Jui Wang wrote:
> These patches fix the lockdep splat reported in this thread:
> https://lore.kernel.org/lkml/20220822164404.57952727@gandalf.local.home/
> 
> 

Why not cc: all of the developers involved in this 00/10 email?

I would need approval from them to be able to take this.

Also, is the lockdep splat correct?  Or is it a false positive?  And if
correct, is it something that you can actually trigger somehow?

thanks,

greg k-h

  parent reply	other threads:[~2023-03-10 10:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03  9:23 [PATCH 00/10] Backport patches to fix lockdep splat in 6.1 Cheng-Jui Wang
2023-03-03  9:23 ` [PATCH 01/10] cpuidle/poll: Ensure IRQs stay disabled after cpuidle_state::enter() calls Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23 ` [PATCH 02/10] cpuidle, riscv: Push RCU-idle into driver Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-07  0:48   ` patchwork-bot+linux-riscv
2023-03-07  0:48     ` patchwork-bot+linux-riscv
2023-03-07  0:48     ` patchwork-bot+linux-riscv
2023-03-03  9:23 ` [PATCH 03/10] cpuidle, tegra: " Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23 ` [PATCH 04/10] cpuidle, psci: " Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-10  8:47   ` Geert Uytterhoeven
2023-03-10  8:47     ` Geert Uytterhoeven
2023-03-03  9:23 ` [PATCH 05/10] cpuidle, ARM/imx6: " Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23 ` [PATCH 06/10] cpuidle, OMAP3: " Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23 ` [PATCH 07/10] cpuidle, armada: " Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23 ` [PATCH 08/10] cpuidle, OMAP4: " Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23 ` [PATCH 09/10] cpuidle, dt: " Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23 ` [PATCH 10/10] cpuidle: Fix ct_idle_*() usage Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-03  9:23   ` Cheng-Jui Wang
2023-03-10 10:12 ` Greg KH [this message]
2023-03-10 10:13   ` [PATCH 00/10] Backport patches to fix lockdep splat in 6.1 Greg KH

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=ZAsClzHcFVs+Hztr@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cheng-jui.wang@mediatek.com \
    --cc=stable@vger.kernel.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 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.