From: Tom Rini <trini@konsulko.com>
To: Harsha Vardhan V M <h-vm@ti.com>
Cc: u-boot@lists.denx.de
Subject: Re: [RFC PATCH 3/4] drivers: k3_fuse: Add fuse sub-system func calls
Date: Thu, 13 Mar 2025 10:19:27 -0600 [thread overview]
Message-ID: <20250313161927.GG2640854@bill-the-cat> (raw)
In-Reply-To: <20250313115517.1181829-4-h-vm@ti.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On Thu, Mar 13, 2025 at 05:25:16PM +0530, Harsha Vardhan V M wrote:
> Add K3_FUSE config option to add and enable fuse sub-system
> implementation function calls.
>
> Signed-off-by: Harsha Vardhan V M <h-vm@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
And can you please file an issue on
https://source.denx.de/u-boot/u-boot/-/issues/ to further clean-up the
fuse related Kconfig symbols and logic? What we have today is a bit odd,
but it's I think easier for me to go and shuffle things than explain how
I think it should be. Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-03-13 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 11:55 [RFC PATCH 0/4] cmd: fuse: Introduce fuse writebuff sub-system and clean up Harsha Vardhan V M
2025-03-13 11:55 ` [RFC PATCH 1/4] cmd: fuse: Remove custom string functions Harsha Vardhan V M
2025-03-13 16:15 ` Tom Rini
2025-03-14 13:43 ` [EXTERNAL] " Harsha Vardhan V M
2025-03-14 14:09 ` Tom Rini
2025-03-17 8:59 ` Harsha Vardhan V M
2025-03-17 14:23 ` Tom Rini
2025-03-13 11:55 ` [RFC PATCH 2/4] cmd: fuse: Add fuse writebuff sub-system command Harsha Vardhan V M
2025-03-13 16:18 ` Tom Rini
2025-03-14 13:45 ` [EXTERNAL] " Harsha Vardhan V M
2025-03-13 11:55 ` [RFC PATCH 3/4] drivers: k3_fuse: Add fuse sub-system func calls Harsha Vardhan V M
2025-03-13 16:19 ` Tom Rini [this message]
2025-03-17 9:11 ` Harsha Vardhan V M
2025-03-13 11:55 ` [RFC PATCH 4/4] docs: fuse: Add fuse writebuff cmd docs Harsha Vardhan V M
2025-03-13 16:20 ` Tom Rini
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=20250313161927.GG2640854@bill-the-cat \
--to=trini@konsulko.com \
--cc=h-vm@ti.com \
--cc=u-boot@lists.denx.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