From: Tom Rini <trini@konsulko.com>
To: alice.guo@oss.nxp.com
Cc: u-boot@lists.denx.de, alice.guo@nxp.com, ye.li@nxp.com,
peng.fan@nxp.com, akashi.tkhro@gmail.com, sjg@chromium.org,
festevam@gmail.com, marex@denx.de
Subject: Re: [PATCH v1] scmi_protocols: Update discover list protocol message
Date: Mon, 7 Oct 2024 11:04:49 -0600 [thread overview]
Message-ID: <20241007170449.GA4737@bill-the-cat> (raw)
In-Reply-To: <20241006095022.2800641-1-alice.guo@oss.nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Sun, Oct 06, 2024 at 05:50:22PM +0800, alice.guo@oss.nxp.com wrote:
> From: Ye Li <ye.li@nxp.com>
>
> When work with System Manager, System Manager provides vendor specific
> protocol, so the protocol array size is not enough.
>
> Signed-off-by: Ye Li <ye.li@nxp.com>
> Signed-off-by: Alice Guo <alice.guo@nxp.com>
> ---
> include/scmi_protocols.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/scmi_protocols.h b/include/scmi_protocols.h
> index 43b66be00a..6204ce076e 100644
> --- a/include/scmi_protocols.h
> +++ b/include/scmi_protocols.h
> @@ -146,7 +146,7 @@ struct scmi_base_discover_impl_version_out {
> struct scmi_base_discover_list_protocols_out {
> s32 status;
> u32 num_protocols;
> - u32 protocols[3];
> + u32 protocols[4];
> };
>
> /**
Changing a constant from 3 to 4 isn't good, please define something and
add a comment explaining what the constant means so it'll be clear
when/why someone changes it to 5. Thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-10-07 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 9:50 [PATCH v1] scmi_protocols: Update discover list protocol message alice.guo
2024-10-07 17:04 ` Tom Rini [this message]
2024-10-07 17:49 ` Fabio Estevam
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=20241007170449.GA4737@bill-the-cat \
--to=trini@konsulko.com \
--cc=akashi.tkhro@gmail.com \
--cc=alice.guo@nxp.com \
--cc=alice.guo@oss.nxp.com \
--cc=festevam@gmail.com \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=ye.li@nxp.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