From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
"Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>,
"Hall, Christopher S" <christopher.s.hall@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Keller, Jacob E" <jacob.e.keller@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Saarinen, Jani" <jani.saarinen@intel.com>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
regressions@lists.linux.dev,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Subject: Re: [Intel-wired-lan] [REGRESSION] v6.15-rc3: 1a931c4f5e68 ("igc: add lock preventing multiple simultaneous PTM transactions")
Date: Wed, 07 May 2025 18:31:21 +0300 [thread overview]
Message-ID: <87a57ov3na.fsf@intel.com> (raw)
In-Reply-To: <2cc74d66-9bd7-4876-a17d-c71f03910c4d@intel.com>
On Tue, 06 May 2025, Tony Nguyen <anthony.l.nguyen@intel.com> wrote:
> On 5/5/2025 3:53 AM, Jani Nikula wrote:
>> On Mon, 28 Apr 2025, "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com> wrote:
>>> Hello Christopher,
>>>
>>> This mail is regarding a regression we are seeing in our CI runs[1] on drm-tip[2] repository.
>>
>> The regressing commit is in v6.15-rc3. Updated subject and Cc'd
>> regression tracking.
>>
>> BR,
>> Jani.
>
> Hi Jani,
>
> This should be resolved with commit c7d6cb96d5c3 ("igc: fix lock order
> in igc_ptp_reset") in v6.15-rc5.
Thanks for the follow-up.
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2025-05-07 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 6:02 Regression on drm-tip Borah, Chaitanya Kumar
2025-05-05 10:53 ` [REGRESSION] v6.15-rc3: 1a931c4f5e68 ("igc: add lock preventing multiple simultaneous PTM transactions") Jani Nikula
2025-05-06 16:24 ` [Intel-wired-lan] " Tony Nguyen
2025-05-07 15:31 ` Jani Nikula [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=87a57ov3na.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jacob.e.keller@intel.com \
--cc=jani.saarinen@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=suresh.kumar.kurmi@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;
as well as URLs for NNTP newsgroup(s).