From: "Guo, Junfeng" <junfeng.guo@intel.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>,
Rushil Gupta <rushilg@google.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "joshwash@google.com" <joshwash@google.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jeroen de Borst <jeroendb@google.com>,
Aaron Conole <aconole@redhat.com>, dpdklab <dpdklab@iol.unh.edu>
Subject: RE: [PATCH] net/gve: Check whether the driver is compatible with the device presented.
Date: Tue, 18 Apr 2023 05:30:43 +0000 [thread overview]
Message-ID: <DM6PR11MB37230645156997D13961AE85E79D9@DM6PR11MB3723.namprd11.prod.outlook.com> (raw)
In-Reply-To: <61ba3937-16b3-53ab-ec82-445aef92a3a0@amd.com>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@amd.com>
> Sent: Friday, April 14, 2023 23:40
> To: Guo, Junfeng <junfeng.guo@intel.com>; Rushil Gupta
> <rushilg@google.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>
> Cc: joshwash@google.com; dev@dpdk.org; Jeroen de Borst
> <jeroendb@google.com>; Aaron Conole <aconole@redhat.com>;
> dpdklab <dpdklab@iol.unh.edu>
> Subject: Re: [PATCH] net/gve: Check whether the driver is compatible
> with the device presented.
>
> On 4/14/2023 10:05 AM, Guo, Junfeng wrote:
> > Hi Ferruh,
> >
> > Here is the summary of the dependency of related patches:
> >
> > P1: necessary headers update
> > https://patchwork.dpdk.org/project/dpdk/list/?series=27647&state=*
> > P2: minor update for base code
> > https://patchwork.dpdk.org/project/dpdk/list/?series=27653&state=*
> > P3: gve PMD enhancement
> > https://patchwork.dpdk.org/project/dpdk/list/?series=27687&state=*
> > P4: add new AdminQ cmd to verify drv cap
> > https://patchwork.dpdk.org/project/dpdk/list/?series=27703&state=*
> >
> > The merging order could be: P1 > P2 > P3 > P4, due to the dependency.
> > Just to inform you about this here. Thanks for the review!
> >
>
> Thanks Junfeng, this is useful.
>
> Btw, we have a defined syntax for this [1], having it in commit log may
> help automated CI to parse it and apply in correct order (when it is
> fully supported in CI :) )
>
>
> [1]
> https://doc.dpdk.org/guides/contributing/patches.html#patch-
> dependencies
>
> Depends-on: series-NNNNN ("Title of the series")
> or
> Depends-on: patch-NNNNN ("Title of the patch")
>
> And I just recognized that syntax is not clear for multiple dependency
> case, we should define it better.
Sure, we will try this in the coming version patches.
Really a good solution for the patch dependencies!
Thanks for the enhancement!
next prev parent reply other threads:[~2023-04-18 5:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 5:14 Rushil Gupta
2023-04-14 9:05 ` Guo, Junfeng
2023-04-14 15:40 ` Ferruh Yigit
2023-04-18 5:30 ` Guo, Junfeng [this message]
2023-04-26 21:37 ` Rushil Gupta
2023-05-04 15:06 ` Ferruh Yigit
2023-05-08 6:23 ` Rushil Gupta
2023-05-08 16:00 ` Ferruh Yigit
2023-05-08 19:22 ` Rushil Gupta
2023-05-08 19:15 ` [v2] net/gve: check driver compatibility Rushil Gupta
2023-05-17 16:58 ` Ferruh Yigit
2023-05-18 17:41 ` Rushil Gupta
2023-05-19 7:15 ` [v3] " Rushil Gupta
2023-05-19 7:23 ` [PATCH] " Rushil Gupta
2023-05-19 7:26 ` Rushil Gupta
2023-05-19 7:41 ` Rushil Gupta
2023-05-19 10:04 ` Ferruh Yigit
2023-05-19 16:15 ` Rushil Gupta
2023-05-19 19:54 ` [v4] " Rushil Gupta
2023-05-19 20:46 ` Rushil Gupta
2023-05-19 20:56 ` Stephen Hemminger
2023-05-20 16:44 ` Rushil Gupta
2023-05-22 8:52 ` Ferruh Yigit
2023-05-22 15:45 ` Rushil Gupta
2023-05-23 10:20 ` Ferruh Yigit
2023-05-23 10:21 ` Ferruh Yigit
2023-05-24 17:14 ` Rushil Gupta
2023-05-31 16:40 ` Rushil Gupta
2023-05-24 17:13 ` [v5] " Rushil Gupta
2023-05-31 17:04 ` Ferruh Yigit
2023-05-18 17:40 ` [v3] " Rushil Gupta
2023-05-08 19:14 ` [v2] " Rushil Gupta
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=DM6PR11MB37230645156997D13961AE85E79D9@DM6PR11MB3723.namprd11.prod.outlook.com \
--to=junfeng.guo@intel.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=ferruh.yigit@amd.com \
--cc=jeroendb@google.com \
--cc=jingjing.wu@intel.com \
--cc=joshwash@google.com \
--cc=qi.z.zhang@intel.com \
--cc=rushilg@google.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;
as well as URLs for NNTP newsgroup(s).