From: Bjorn Helgaas <helgaas@kernel.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: bugzilla-daemon@kernel.org,
"Malte Schröder" <malte+lkml@tnxip.de>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [Bug 220775] snd_ctxfi fails init since 6.18-rc1
Date: Mon, 26 Jan 2026 11:33:52 -0600 [thread overview]
Message-ID: <20260126173352.GA245281@bhelgaas> (raw)
In-Reply-To: <e0e34d7a-8919-f3f9-1136-23e6e9f7b203@linux.intel.com>
On Mon, Jan 26, 2026 at 02:03:52PM +0200, Ilpo Järvinen wrote:
> On Mon, 26 Jan 2026, bugzilla-daemon@kernel.org wrote:
>
> > https://bugzilla.kernel.org/show_bug.cgi?id=220775
> >
> > --- Comment #27 from Malte (malte+kbz@tnxip.de) ---
> > Did this patch make it into 6.19? I just tried -rc7 and the issue is still
> > there.
>
> Unfortunately, it's still not applied:
>
> https://patchwork.kernel.org/project/linux-pci/list/?series=1035150
>
> (I also checked pci/resource branch and it doesn't appear there).
>
> The fixes used to be in a separate series but I've so many dependencies
> between my pending work I had to put them into that larger series (in
> hopes that it would have all gotten applied in this cycle).
>
> The regression fixes (this and some ppc (IIRC) regression) are in the
> first 5 commits. I'm not sure if taking the entire series this late is
> a good idea even if the rest of the series should be most no functional
> changes in preparation to some work not yet submitted.
Sorry, I completely missed this. It looks like we do have an extra
week this cycle, so two weeks until v6.19 final. I put these on
pci/resource and hopefully we can make it for v6.20.
Bjorn
prev parent reply other threads:[~2026-01-26 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-220775-228660@https.bugzilla.kernel.org/>
[not found] ` <bug-220775-228660-pG3cpJLOFZ@https.bugzilla.kernel.org/>
2026-01-26 12:03 ` [Bug 220775] snd_ctxfi fails init since 6.18-rc1 Ilpo Järvinen
2026-01-26 17:33 ` Bjorn Helgaas [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=20260126173352.GA245281@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=bugzilla-daemon@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=malte+lkml@tnxip.de \
/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