From: Thomas Gleixner <tglx@linutronix.de>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>,
linuxarm@huawei.com, rafael.j.wysocki@intel.com,
guohanjun@huawei.com, gshan@redhat.com, miguel.luis@oracle.com,
catalin.marinas@arm.com,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Bowman, Terry" <Terry.bowman@amd.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Subject: Re: 6.11/regression/bisected - The commit c1385c1f0ba3 caused a new possible recursive locking detected warning at computer boot.
Date: Fri, 26 Jul 2024 22:35:47 +0200 [thread overview]
Message-ID: <878qxnvql8.ffs@tglx> (raw)
In-Reply-To: <20240726190119.00002557@Huawei.com>
On Fri, Jul 26 2024 at 19:01, Jonathan Cameron wrote:
> I tested it on an emulated setup with your changes on top of
> mainline as of today and the issue is resolved.
>
> Would you mind posting a formal patch? Or I can do it on Monday if that's
> easier for you.
Go for it. I have enough stuff on my plate to deal with :)
Suggested-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2024-07-26 20:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 19:36 6.11/regression/bisected - The commit c1385c1f0ba3 caused a new possible recursive locking detected warning at computer boot Mikhail Gavrilov
2024-07-23 10:24 ` Jonathan Cameron
2024-07-23 17:20 ` Jonathan Cameron
2024-07-25 17:13 ` Jonathan Cameron
2024-07-25 22:30 ` Mikhail Gavrilov
2024-07-26 15:07 ` Terry Bowman
2024-07-26 16:37 ` Jonathan Cameron
2024-07-26 17:59 ` Jonathan Cameron
2024-07-26 16:26 ` Thomas Gleixner
2024-07-26 17:14 ` Jonathan Cameron
2024-07-26 18:01 ` Jonathan Cameron
2024-07-26 20:35 ` Thomas Gleixner [this message]
2024-07-27 7:13 ` Mikhail Gavrilov
2024-08-03 15:48 ` Hans de Goede
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=878qxnvql8.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Jonathan.Cameron@Huawei.com \
--cc=Terry.bowman@amd.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=gshan@redhat.com \
--cc=guohanjun@huawei.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=miguel.luis@oracle.com \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=mingo@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=regressions@lists.linux.dev \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox