From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: <brauner@kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Saarinen, Jani" <jani.saarinen@intel.com>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: REGRESSION on drm-tip
Date: Fri, 28 Nov 2025 13:16:44 +0530 [thread overview]
Message-ID: <860117f0-d8b1-4f4b-8448-d8fd83634c4f@intel.com> (raw)
In-Reply-To: <aSjY8et1QDyvFq9x@intel.com>
On 11/28/2025 4:34 AM, Ville Syrjälä wrote:
>> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>> commit a3f8f8662771285511ae26c4c8d3ba1cd22159b9
>> Author: Christian Brauner<brauner@kernel.org>
>> Date: Wed Nov 5 14:39:45 2025 +0100
>>
>> power: always freeze efivarfs
> - if (freeze_all_ptr && !(sb->s_type->fs_flags & FS_POWER_FREEZE))
> + if (!freeze_all_ptr && !(sb->s_type->fs_flags & FS_POWER_FREEZE))
>
> ?
This change helps.
@Christian do you plan to send out a fix for it?
Thank you Ville for pointing it out.
Regards
Chaitanya
next prev parent reply other threads:[~2025-11-28 7:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 6:25 REGRESSION on drm-tip Borah, Chaitanya Kumar
2025-11-27 16:01 ` Saarinen, Jani
2025-11-27 16:06 ` Saarinen, Jani
2025-11-27 23:04 ` Ville Syrjälä
2025-11-28 7:46 ` Borah, Chaitanya Kumar [this message]
2025-12-05 10:14 ` Christian Brauner
2025-12-01 16:13 ` Saarinen, Jani
2025-12-03 13:34 ` BISECTED REGRESSION on v6.18 (was: REGRESSION on drm-tip) Jani Nikula
2025-12-03 13:36 ` Jani Nikula
2025-12-03 13:40 ` Rafael J. Wysocki
2025-12-05 10:14 ` REGRESSION on drm-tip Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2025-04-28 6:02 Regression " Borah, Chaitanya Kumar
2025-03-13 8:51 Borah, Chaitanya Kumar
2025-03-13 9:30 ` Baolu Lu
2025-03-13 14:23 ` Baolu Lu
2025-03-14 9:04 ` Borah, Chaitanya Kumar
2025-03-16 2:33 ` Baolu Lu
2025-03-16 7:27 ` Borah, Chaitanya Kumar
2025-03-16 8:03 ` Baolu Lu
2025-03-16 10:01 ` Borah, Chaitanya Kumar
2025-03-17 4:04 ` Baolu Lu
2025-03-22 20:59 ` Lucas De Marchi
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=860117f0-d8b1-4f4b-8448-d8fd83634c4f@intel.com \
--to=chaitanya.kumar.borah@intel.com \
--cc=brauner@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=suresh.kumar.kurmi@intel.com \
--cc=ville.syrjala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox