public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mahesh Rao <mahesh.rao@altera.com>
To: Dinh Nguyen <dinguyen@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Richard Gong <richard.gong@intel.com>,
	Alan Tull <atull@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Matthew Gerlach <matthew.gerlach@altera.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RESEND v6 0/4] stratix10: Add framework for asynchronous communication with SDM
Date: Mon, 27 Oct 2025 17:28:50 +0530	[thread overview]
Message-ID: <9d427a5b-952f-4140-bec3-e8f22b34985e@altera.com> (raw)
In-Reply-To: <aab92ea9-60a4-43e5-bbee-96484d15f3a7@kernel.org>

Hi Dinh,

On 20-10-2025 09:33 pm, Dinh Nguyen wrote:
> 
> 
> On 9/24/25 02:39, Mahesh Rao via B4 Relay wrote:
>> The patch set includes the following changes:
>>
>> - Add protection for querying memory objects in multi-threaded flow.
>> - Add support to generate and maintain message id and client id for
>>    asynchronous communication with SDM.
>> - Add framework to communicate with Secure Device Manager (SDM)
>>    asynchronously by sending a request and polling for response.
>> - Add commands for performing Remote System Update (RSU) operations
>>    asynchronously.
>> - Migrate RSU driver to use the asynchronous communication framework.
>>
>> ---
>> - Link to v6: https://lore.kernel.org/r/20250901-sip_svc_upstream- 
>> v6-0-b4db7f07cbb2@altera.com
>>
>> Changes in v6:


>> - Added support for RSU commands to asynchronously
>>    communicate with SDM.
>> - Migrated RSU driver to use the supported
>>    asynchronous commands
> 
> Can you please rebase this series on my latest tree:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git/log/? 
> h=svc_driver_for_v6.19
> 
> Patch 2 is not applying correctly.

Sorry for the delayed response, as I was on vacation last week.

Sure, I will rebase the patchset onto svc_driver_for_v6.19 and re share.

> 
> Thanks,
> Dinh


      reply	other threads:[~2025-10-27 11:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24  7:39 [PATCH RESEND v6 0/4] stratix10: Add framework for asynchronous communication with SDM Mahesh Rao via B4 Relay
2025-09-24  7:39 ` [PATCH RESEND v6 1/4] firmware: stratix10-svc: Add mutex in stratix10 memory management Mahesh Rao via B4 Relay
2025-09-24  7:39 ` [PATCH RESEND v6 2/4] firmware: stratix10-svc: Add support for async communication Mahesh Rao via B4 Relay
2025-09-24  7:39 ` [PATCH RESEND v6 3/4] firmware: stratix10-svc: Add support for RSU commands in asynchronous framework Mahesh Rao via B4 Relay
2025-09-24  7:39 ` [PATCH RESEND v6 4/4] firmware: stratix10-rsu: Migrate RSU driver to use stratix10 " Mahesh Rao via B4 Relay
2025-10-20 16:03 ` [PATCH RESEND v6 0/4] stratix10: Add framework for asynchronous communication with SDM Dinh Nguyen
2025-10-27 11:58   ` Mahesh Rao [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=9d427a5b-952f-4140-bec3-e8f22b34985e@altera.com \
    --to=mahesh.rao@altera.com \
    --cc=atull@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.gerlach@altera.com \
    --cc=richard.gong@intel.com \
    --cc=robh@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