patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: oss-drivers <oss-drivers@corigine.com>,
	Xinying Yu <xinying.yu@nephogine.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	Long Wu <Long.Wu@nephogine.com>,
	Nole Zhang <peng.zhang@corigine.com>
Subject: RE: [PATCH 03/10] vdpa/nfp: fix the logic of reconfiguration
Date: Fri, 14 Jun 2024 02:30:40 +0000	[thread overview]
Message-ID: <SJ0PR13MB5545892A3AC1E5765837EB209EC22@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <4249e219-5aac-4998-8844-677bddd35585@redhat.com>

> On 4/26/24 09:48, Chaoyong He wrote:
> > From: Xinying Yu <xinying.yu@corigine.com>
> >
> > The ctrl words of vDPA is locate on the extend word, so should use the
> > 'nfp_ext_reconfig()' rather than 'nfp_reconfig()'.
> 
> located*
> extended*
> 
> so it should*
> 

Will fix in the v2 patch series.
Thanks for your review.

> >
> > Also replace the misuse of 'NFP_NET_CFG_CTRL_SCATTER' macro with
> > 'NFP_NET_CFG_CTRL_VIRTIO'.
> >
> > Fixes: b47a0373903f ("vdpa/nfp: add datapath update")
> > Cc: chaoyong.he@corigine.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Xinying Yu <xinying.yu@corigine.com>
> > Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> > Reviewed-by: Long Wu <long.wu@corigine.com>
> > Reviewed-by: Peng Zhang <peng.zhang@corigine.com>
> > ---
> >   drivers/common/nfp/nfp_common_ctrl.h |  1 +
> >   drivers/vdpa/nfp/nfp_vdpa_core.c     | 16 ++++++++++++----
> >   2 files changed, 13 insertions(+), 4 deletions(-)
> >
> 
> With commit message fixed (I can do it if only change needed in the
> series):
> 
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> 
> Thanks,
> Maxime


  reply	other threads:[~2024-06-14  2:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240426074831.1729792-1-chaoyong.he@corigine.com>
2024-04-26  7:48 ` [PATCH 02/10] vdpa/nfp: fix logic in hardware init Chaoyong He
2024-06-13 11:41   ` Maxime Coquelin
2024-04-26  7:48 ` [PATCH 03/10] vdpa/nfp: fix the logic of reconfiguration Chaoyong He
2024-06-13 11:43   ` Maxime Coquelin
2024-06-14  2:30     ` Chaoyong He [this message]
     [not found] ` <20240614070120.2663160-1-chaoyong.he@corigine.com>
2024-06-14  7:01   ` [PATCH v2 02/11] vdpa/nfp: fix logic in hardware init Chaoyong He
2024-06-14  7:01   ` [PATCH v2 03/11] vdpa/nfp: fix the logic of reconfiguration Chaoyong He
     [not found]   ` <20240617062708.2932037-1-chaoyong.he@corigine.com>
2024-06-17  6:26     ` [PATCH v3 02/11] vdpa/nfp: fix logic in hardware init Chaoyong He
2024-06-18  7:50       ` Maxime Coquelin
2024-06-17  6:27     ` [PATCH v3 03/11] vdpa/nfp: fix the logic of reconfiguration Chaoyong He
2024-06-18  7:51       ` Maxime Coquelin
     [not found]     ` <20240805021248.1051198-1-chaoyong.he@corigine.com>
2024-08-05  2:12       ` [PATCH v4 02/11] vdpa/nfp: fix logic in hardware init Chaoyong He
2024-08-05  2:12       ` [PATCH v4 03/11] vdpa/nfp: fix the logic of reconfiguration Chaoyong He

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=SJ0PR13MB5545892A3AC1E5765837EB209EC22@SJ0PR13MB5545.namprd13.prod.outlook.com \
    --to=chaoyong.he@corigine.com \
    --cc=Long.Wu@nephogine.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=oss-drivers@corigine.com \
    --cc=peng.zhang@corigine.com \
    --cc=stable@dpdk.org \
    --cc=xinying.yu@nephogine.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).