From: Leonardo Costa <leoreis.costa@gmail.com>
To: kwilczynski@kernel.org
Cc: leonardo.costa@toradex.com, achill@achill.org,
akpm@linux-foundation.org, bhelgaas@google.com,
broonie@kernel.org, conor@kernel.org, f.fainelli@gmail.com,
francesco@dolcini.it, gregkh@linuxfoundation.org,
hargar@microsoft.com, hongxing.zhu@nxp.com, jonathanh@nvidia.com,
leoreis.costa@gmail.com, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux@roeck-us.net, lkft-triage@lists.linaro.org,
patches@kernelci.org, patches@lists.linux.dev,
pavel@nabladev.com, rwarsow@gmx.de, ryanmatthews@fastmail.com,
shuah@kernel.org, sr@sladewatkins.com, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.6 000/508] 6.6.141-rc1 review
Date: Thu, 28 May 2026 09:56:05 -0300 [thread overview]
Message-ID: <20260528125605.255471-1-leoreis.costa@gmail.com> (raw)
In-Reply-To: <20260526183025.GA1285841@rocinante>
Hello Krzysztof,
> > When you have a moment, consider changes from the following series:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/log/?h=sysfs
> >
> > Test, and let us know if this fixes the problem for you.
> >
> > I would appreciate if you could test this for us.
>
> I realise that 6.6 is a bit of a far cry from changes against the upcoming
> 7.2 release, so you might have to massage the series/patches into sensible
> state, so to speak.
>
> Let me know if testing is too involved, given the need to potentially
> backport a lot. I will think of something.
I tried backporting the patches to do a test, but it turned out giving too many
errors due to the different context. Since it's not really breaking anything,
we'll leave it as it currently is.
Either way thanks a lot for clarifying this! It's good knowing the patches
where this issue was addressed.
Leonardo
next prev parent reply other threads:[~2026-05-28 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 16:17 Greg Kroah-Hartman
2026-05-20 19:11 ` Brett A C Sheffield
2026-05-20 20:33 ` Florian Fainelli
2026-05-21 12:55 ` Sasha Levin
2026-05-21 5:15 ` Francesco Dolcini
2026-05-21 5:22 ` Francesco Dolcini
2026-05-26 18:05 ` Leonardo Costa
2026-05-26 18:25 ` Krzysztof Wilczyński
2026-05-26 18:33 ` Krzysztof Wilczyński
2026-05-28 12:56 ` Leonardo Costa [this message]
2026-05-21 9:54 ` Pavel Machek
2026-05-21 10:36 ` Mark Brown
2026-05-21 21:57 ` Peter Schneider
2026-05-22 0:38 ` Ron Economos
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=20260528125605.255471-1-leoreis.costa@gmail.com \
--to=leoreis.costa@gmail.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=francesco@dolcini.it \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=hongxing.zhu@nxp.com \
--cc=jonathanh@nvidia.com \
--cc=kwilczynski@kernel.org \
--cc=leonardo.costa@toradex.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=ryanmatthews@fastmail.com \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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
Powered by JetHome