mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chan, Genevieve" <genevieve.chan@altera.com>
To: Dinh Nguyen <dinguyen@kernel.org>, linux-kernel@vger.kernel.org
Cc: Tze Yee Ng <tze.yee.ng@altera.com>,
	Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>,
	Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
Subject: Re: [PATCH] firmware: stratix10-svc: fix FCS SMC call kernel-doc
Date: Thu, 2 Jul 2026 16:31:15 +0800	[thread overview]
Message-ID: <b8d09557-d27e-4aaa-80fd-b2a695ea2fff@altera.com> (raw)
In-Reply-To: <73cd6456-6c6d-48c8-ad33-d61a3a64a5ef@kernel.org>

V2 patch is submitted: https://lore.kernel.org/all/20260702082844.9648-1-genevieve.chan@altera.com/

Thanks,
Genevieve Chan

On 29/6/2026 10:02 pm, Dinh Nguyen wrote:
> 
> 
> On 6/23/26 04:10, genevieve.chan@altera.com wrote:
>> From: Genevieve Chan <genevieve.chan@altera.com>
>>
>> Correct the kernel-doc for INTEL_SIP_SMC_FCS_SEND_CERTIFICATE to
>> describe an async call instead of sync, and fix incorrect return
>> status macro names
>> (INTEL_SIP_SMC_FCS_REJECTED -> INTEL_SIP_SMC_REJECTED).
>>
>> For INTEL_SIP_SMC_FCS_GET_PROVISION_DATA, align the documented
>> return status macros with the standard values
>> (INTEL_SIP_SMC_STATUS_ERROR and INTEL_SIP_SMC_STATUS_REJECTED)
>> and document the full async return register usage in a1-a3:
>> mailbox error code, physical address of the fuse/key hash structure,
>> and structure size.
>>
>> Signed-off-by: Genevieve Chan <genevieve.chan@altera.com>
>> ---
>>   include/linux/firmware/intel/stratix10-smc.h | 12 +++++++-----
>>   1 file changed, 7 insertions(+), 5 deletions(-)
>>
> 
> If this is a fix, you forgot to include the Fixes tag and Cc: stable.
> 
> Please refer to : Documentation/process/stable-kernel-rules.rst
> 
> Thanks,
> Dinh


      reply	other threads:[~2026-07-02  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  9:10 genevieve.chan
2026-06-29 14:02 ` Dinh Nguyen
2026-07-02  8:31   ` Chan, Genevieve [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=b8d09557-d27e-4aaa-80fd-b2a695ea2fff@altera.com \
    --to=genevieve.chan@altera.com \
    --cc=adrian.ho.yin.ng@altera.com \
    --cc=dinguyen@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
    --cc=tze.yee.ng@altera.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

Powered by JetHome