public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	WANG Xuerui <kernel@xen0n.name>
Subject: Re: Patch "LoongArch: Init acpi_gbl_use_global_lock to false" has been added to the 6.12-stable tree
Date: Thu, 16 Oct 2025 16:37:25 +0200	[thread overview]
Message-ID: <2025101611-removed-imperfect-854d@gregkh> (raw)
In-Reply-To: <CAAhV-H5ph0b3pf2PQV3hw83vPxKO-9Vba=XUCFRON1BUh7Y4oQ@mail.gmail.com>

On Thu, Oct 16, 2025 at 10:30:20PM +0800, Huacai Chen wrote:
> Hi, Sasha,
> 
> On Wed, Oct 15, 2025 at 7:42 PM Sasha Levin <sashal@kernel.org> wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> >     LoongArch: Init acpi_gbl_use_global_lock to false
> >
> > to the 6.12-stable tree which can be found at:
> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> >      loongarch-init-acpi_gbl_use_global_lock-to-false.patch
> > and it can be found in the queue-6.12 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
> >
> Please also backport feb8ae81b2378b75a99c81d3156 ("ACPICA: Allow to
> skip Global Lock initialization") as a dependency for all stable
> branches.
> 

Now queued up, thanks.

greg k-h

      reply	other threads:[~2025-10-16 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251015114243.1341568-1-sashal@kernel.org>
2025-10-16 14:30 ` Patch "LoongArch: Init acpi_gbl_use_global_lock to false" has been added to the 6.12-stable tree Huacai Chen
2025-10-16 14:37   ` Greg KH [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=2025101611-removed-imperfect-854d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=chenhuacai@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=stable-commits@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox