From: Timur Tabi <ttabi@nvidia.com>
To: "gary@garyguo.net" <gary@garyguo.net>,
Alexandre Courbot <acourbot@nvidia.com>,
"dakr@kernel.org" <dakr@kernel.org>,
John Hubbard <jhubbard@nvidia.com>
Cc: Shashank Sharma <shashanks@nvidia.com>,
"lossin@kernel.org" <lossin@kernel.org>,
"boqun.feng@gmail.com" <boqun.feng@gmail.com>,
"a.hindborg@kernel.org" <a.hindborg@kernel.org>,
Zhi Wang <zhiw@nvidia.com>, "simona@ffwll.ch" <simona@ffwll.ch>,
"tmgross@umich.edu" <tmgross@umich.edu>,
"alex.gaynor@gmail.com" <alex.gaynor@gmail.com>,
"nova-gpu@lists.linux.dev" <nova-gpu@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ojeda@kernel.org" <ojeda@kernel.org>,
"bjorn3_gh@protonmail.com" <bjorn3_gh@protonmail.com>,
Eliot Courtney <ecourtney@nvidia.com>,
"airlied@gmail.com" <airlied@gmail.com>,
"aliceryhl@google.com" <aliceryhl@google.com>,
"bhelgaas@google.com" <bhelgaas@google.com>,
Alistair Popple <apopple@nvidia.com>
Subject: Re: [PATCH v2] gpu: nova-core: clarify FSP ordering in the chipset table
Date: Fri, 12 Jun 2026 15:43:34 +0000 [thread overview]
Message-ID: <30e7305062676b72b7400a7e2cf48ff8e78139d4.camel@nvidia.com> (raw)
In-Reply-To: <DJ723OXGM3QC.2YNSLXNPCLKC9@garyguo.net>
On Fri, 2026-06-12 at 13:06 +0100, Gary Guo wrote:
> This would be inconsistent with the derived `PartialOrd` implementation?
>
> If we consider Hopper to be after Ada, then we should be able to `assert!(GH100 > AD102);`
This is a comment about how we describe things, not how the code works. It's because we
frequently say "Hopper or later" to describe our GPUs' capabilities.
next prev parent reply other threads:[~2026-06-12 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 4:04 [PATCH v2] gpu: nova-core: clarify FSP ordering in the chipset table John Hubbard
2026-06-12 12:06 ` Gary Guo
2026-06-12 15:43 ` Timur Tabi [this message]
2026-06-12 16:07 ` Gary Guo
2026-06-12 16:24 ` Timur Tabi
2026-06-12 17:17 ` John Hubbard
2026-06-12 17:50 ` Timur Tabi
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=30e7305062676b72b7400a7e2cf48ff8e78139d4.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=ecourtney@nvidia.com \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nova-gpu@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=shashanks@nvidia.com \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=zhiw@nvidia.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