From: Greg KH <gregkh@linuxfoundation.org>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Miguel Ojeda <ojeda@kernel.org>,
achill@achill.org, akpm@linux-foundation.org, broonie@kernel.org,
conor@kernel.org, f.fainelli@gmail.com, hargar@microsoft.com,
jonathanh@nvidia.com, linux-kernel@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, shuah@kernel.org,
sr@sladewatkins.com, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
Eliot Courtney <ecourtney@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Alexandre Courbot <acourbot@nvidia.com>,
Alice Ryhl <aliceryhl@google.com>,
nova-gpu@lists.linux.dev
Subject: Re: [PATCH 6.18 0000/1624] 6.18.40-rc2 review
Date: Fri, 24 Jul 2026 13:16:57 +0200 [thread overview]
Message-ID: <2026072417-avalanche-absurd-de3f@gregkh> (raw)
In-Reply-To: <DK68JRVCSLFU.3MCXVFEF3EE5T@kernel.org>
On Thu, Jul 23, 2026 at 10:33:16PM +0200, Danilo Krummrich wrote:
> On Thu Jul 23, 2026 at 5:43 PM CEST, Miguel Ojeda wrote:
> > I suggest dropping commit
> >
> > d8fa174e21c8 ("gpu: nova-core: vbios: read BitToken using FromBytes")
> >
> > for now -- it was not marked for stable, and as far as I know, there are
> > no production users of Nova, especially in stable kernels.
>
> Yes, we can just drop the commit. In general, for now we should only backport
> nova patches that could get into the way of testing stable releases in one or
> the other way.
Ok, I'll just drop all the nova patches from 6.18.y and 7.1.y now as
they were not specifically tagged for stable, but just picked up due to
their Fixes: tags.
thanks,
greg k-h
prev parent reply other threads:[~2026-07-24 11:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260722142910.893804136@linuxfoundation.org>
2026-07-23 15:43 ` [PATCH 6.18 0000/1624] 6.18.40-rc2 review Miguel Ojeda
2026-07-23 20:33 ` Danilo Krummrich
2026-07-24 11:16 ` 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=2026072417-avalanche-absurd-de3f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=acourbot@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=dakr@kernel.org \
--cc=ecourtney@nvidia.com \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jhubbard@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--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