mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yidong Zhang <yidong.zhang@amd.com>
To: Xu Yilun <yilun.xu@linux.intel.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-fpga@vger.kernel.org>,
	<mdf@kernel.org>, <hao.wu@intel.com>, <yilun.xu@intel.com>,
	<lizhi.hou@amd.com>, DMG Karthik <Karthik.DMG@amd.com>,
	Nishad Saraf <nishads@amd.com>,
	Prapul Krishnamurthy <prapulk@amd.com>
Subject: Re: [PATCH V1 1/3] drivers/fpga/amd: Add new driver for AMD Versal PCIe card
Date: Sun, 22 Dec 2024 17:53:30 -0800	[thread overview]
Message-ID: <f9abc70d-2d07-4506-a227-af297eb77058@amd.com> (raw)
In-Reply-To: <Zzw5MOb6dUD6BLYh@yilunxu-OptiPlex-7050>



On 11/18/24 23:07, Xu Yilun wrote:
> 
>>>> +obj-$(CONFIG_AMD_VERSAL_MGMT)                        += amd-vmgmt.o
>>> IMHO the naming vmgmt is hard to understand, any better idea?
>> The "v" stand for Versal. We would change to amd-vpci for Versal based pcie
> "v" + "pci" is quite a misleading term, maybe just versal-pci?

Hi Yilun,

I sent the V2 patch and refactored the driver as versal-pci now.
One more thing that I kept in V2 was the firmware_upload. I forgot to
mention that I'd love to switch to the newly proposed interface once
it is ready. I saw the proposal was now as config_fs and it was not 
merged yet.

Happy Holidays.

Thanks,
David

  parent reply	other threads:[~2024-12-23  1:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-07 22:01 David Zhang
2024-10-07 22:01 ` [PATCH V1 2/3] drivers/fpga/amd: Add communication with firmware David Zhang
2024-10-09  5:29   ` kernel test robot
2024-10-09 10:44   ` kernel test robot
2024-10-18  8:11   ` Xu Yilun
2024-10-18 17:40     ` Zhang, Yidong (David)
2024-11-12  1:29     ` Yidong Zhang
2024-10-07 22:01 ` [PATCH V1 3/3] drivers/fpga/amd: Add remote queue service APIs David Zhang
2024-10-09  7:13   ` kernel test robot
2024-10-09  9:01 ` [PATCH V1 1/3] drivers/fpga/amd: Add new driver for AMD Versal PCIe card kernel test robot
2024-10-18  6:17 ` Xu Yilun
2024-11-12  1:22   ` Yidong Zhang
2024-11-19  7:07     ` Xu Yilun
2024-11-20  6:15       ` Yidong Zhang
2024-12-23  1:53       ` Yidong Zhang [this message]
2023-03-12 18:03         ` Xu Yilun
2024-12-26  6:10           ` Yidong Zhang
2023-03-12 21:30             ` Xu Yilun
2025-01-02  5:30               ` Yidong Zhang

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=f9abc70d-2d07-4506-a227-af297eb77058@amd.com \
    --to=yidong.zhang@amd.com \
    --cc=Karthik.DMG@amd.com \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.hou@amd.com \
    --cc=mdf@kernel.org \
    --cc=nishads@amd.com \
    --cc=prapulk@amd.com \
    --cc=yilun.xu@intel.com \
    --cc=yilun.xu@linux.intel.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
all inboxes | Powered by JetHome®