From: Joel Fernandes <joelagnelf@nvidia.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: Alexandre Courbot <acourbot@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
"aliceryhl@google.com" <aliceryhl@google.com>,
"lossin@kernel.org" <lossin@kernel.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH 0/4] nova-core Improve pin initializer code
Date: Thu, 18 Dec 2025 21:06:22 +0000 [thread overview]
Message-ID: <FB4E7596-3C84-4D65-81F2-57036F725C0C@nvidia.com> (raw)
In-Reply-To: <20251218155239.25243-1-dakr@kernel.org>
> On Dec 18, 2025, at 10:52 AM, Danilo Krummrich <dakr@kernel.org> wrote:
>
> This is a minor series to improve some of the pin initializer code to:
>
> 1. Reduce redundancy caused by Result<impl PinInit<T, Error>> return
> values with pin_init_scope().
>
> 2. Relocate code that technically fits in the pin initializer into the
> initializer itself.
>
> While, thanks to pin_init_scope(), it is also possible to keep it as is,
> moving appropriate code into the initializer has the advantage that it
> structures the dependencies of fields naturally.
>
> For instance, intermediate data that is only needed for a single field goes
> into the initializer block of this field, making it obvious that it is not
> needed by anything else.
>
> On the other hand, intermediate data that is needed for multiple fields to
> initialize remains above the initializer, naturally indicating that it is
> needed my multiple fields.
>
> Danilo Krummrich (4):
> gpu: nova-core: fw: get rid of redundant Result in GspFirmware::new()
> gpu: nova-core: fw: move appropriate code into pin initializer
> gpu: nova-core: gsp: get rid of redundant Result in Gsp::new()
> gpu: nova-core: gsp: move appropriate code into pin initializer
Reviewed-by: Joel Fernandes <joelagnelf@nvidia.com>
thanks,
- Joel
>
> drivers/gpu/nova-core/firmware/gsp.rs | 134 +++++++++++++-------------
> drivers/gpu/nova-core/gpu.rs | 2 +-
> drivers/gpu/nova-core/gsp.rs | 73 +++++++-------
> drivers/gpu/nova-core/gsp/boot.rs | 5 +-
> 4 files changed, 106 insertions(+), 108 deletions(-)
>
>
> base-commit: 97cf6bc0abd381fd84e5d8e978322a62a58fb00e
> --
> 2.52.0
>
next prev parent reply other threads:[~2025-12-18 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 15:50 Danilo Krummrich
2025-12-18 15:50 ` [PATCH 1/4] gpu: nova-core: fw: get rid of redundant Result in GspFirmware::new() Danilo Krummrich
2025-12-18 15:50 ` [PATCH 2/4] gpu: nova-core: fw: move appropriate code into pin initializer Danilo Krummrich
2025-12-18 15:50 ` [PATCH 3/4] gpu: nova-core: gsp: get rid of redundant Result in Gsp::new() Danilo Krummrich
2025-12-18 15:50 ` [PATCH 4/4] gpu: nova-core: gsp: move appropriate code into pin initializer Danilo Krummrich
2025-12-18 21:06 ` Joel Fernandes [this message]
2025-12-29 17:14 ` [PATCH 0/4] nova-core Improve pin initializer code Danilo Krummrich
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=FB4E7596-3C84-4D65-81F2-57036F725C0C@nvidia.com \
--to=joelagnelf@nvidia.com \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rust-for-linux@vger.kernel.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
all inboxes | Powered by JetHome®