From: Bart Van Assche <bvanassche@acm.org>
To: Ajay Neeli <ajay.neeli@amd.com>,
martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
pedrom.sousa@synopsys.com
Cc: alim.akhtar@samsung.com, avri.altman@wdc.com,
linux-scsi@vger.kernel.org, devicetree@vger.kernel.org,
git@amd.com, michal.simek@amd.com, srinivas.goud@amd.com,
radhey.shyam.pandey@amd.com
Subject: Re: [PATCH v2 0/4] ufs: Add support for AMD Versal Gen2 UFS
Date: Wed, 22 Oct 2025 12:39:19 -0700 [thread overview]
Message-ID: <1d02a30b-1450-459c-a4f4-ae795d7dcb27@acm.org> (raw)
In-Reply-To: <20251021113003.13650-1-ajay.neeli@amd.com>
On 10/21/25 4:29 AM, Ajay Neeli wrote:
> Removed patch that utilized reserved bits for vendor-specific interrupts.
Thanks! This second version of this patch series looks good to me.
Bart.
next prev parent reply other threads:[~2025-10-22 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 11:29 [PATCH v2 0/4] ufs: Add support for AMD Versal Gen2 UFS Ajay Neeli
2025-10-21 11:30 ` [PATCH v2 1/4] dt-bindings: ufs: amd-versal2: Add UFS Host Controller for AMD Versal Gen 2 SoC Ajay Neeli
2025-10-22 17:38 ` Conor Dooley
2025-10-21 11:30 ` [PATCH v2 2/4] firmware: xilinx: Add support for secure read/write ioctl interface Ajay Neeli
2025-10-23 7:31 ` Michal Simek
2025-10-21 11:30 ` [PATCH v2 3/4] firmware: xilinx: Add APIs for UFS PHY initialization Ajay Neeli
2025-10-23 7:31 ` Michal Simek
2025-10-21 11:30 ` [PATCH v2 4/4] ufs: amd-versal2: Add UFS support for AMD Versal Gen 2 SoC Ajay Neeli
2025-10-22 19:39 ` Bart Van Assche [this message]
2025-10-30 3:06 ` [PATCH v2 0/4] ufs: Add support for AMD Versal Gen2 UFS Martin K. Petersen
2025-11-03 3:29 ` Martin K. Petersen
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=1d02a30b-1450-459c-a4f4-ae795d7dcb27@acm.org \
--to=bvanassche@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=ajay.neeli@amd.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michal.simek@amd.com \
--cc=pedrom.sousa@synopsys.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=robh@kernel.org \
--cc=srinivas.goud@amd.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