patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>,
	Taekyung Kim <kim.tae.kyung@navercorp.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Pei, Andy" <andy.pei@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Wang, Xiao W" <xiao.w.wang@intel.com>,
	"Xia, Chenbo" <chenbo.xia@intel.com>
Subject: Re: [PATCH v4] vdpa/ifc: fix update_datapath error handling
Date: Thu, 10 Nov 2022 10:42:12 +0100	[thread overview]
Message-ID: <529277ff-9e3e-15e9-d969-3fd68d66378e@redhat.com> (raw)
In-Reply-To: <DM4PR12MB5167FCB7EF0A6CB4B2C58FB4DA019@DM4PR12MB5167.namprd12.prod.outlook.com>



On 11/10/22 10:34, Ali Alnubani wrote:
>> -----Original Message-----
>> From: Maxime Coquelin <maxime.coquelin@redhat.com>
>> Sent: Thursday, November 10, 2022 11:20 AM
>> To: Taekyung Kim <kim.tae.kyung@navercorp.com>; NBU-Contact-Thomas
>> Monjalon (EXTERNAL) <thomas@monjalon.net>; Ali Alnubani
>> <alialnu@nvidia.com>
>> Cc: dev@dpdk.org; Pei, Andy <andy.pei@intel.com>; stable@dpdk.org;
>> Wang, Xiao W <xiao.w.wang@intel.com>; Xia, Chenbo
>> <chenbo.xia@intel.com>
>> Subject: Re: [PATCH v4] vdpa/ifc: fix update_datapath error handling
>>
>> Hi Taekyung,
>>
>> Adding Thomas and Ali who maintains the patchwork instance.
>>
>> On 11/10/22 05:02, Taekyung Kim wrote:
>>> On Thu, Nov 10, 2022 at 01:53:50AM +0000, Xia, Chenbo wrote:
>>>> Hi Kim,
>>>>
>>>>> -----Original Message-----
>>>>> From: Taekyung Kim <kim.tae.kyung@navercorp.com>
>>>>> Sent: Tuesday, November 8, 2022 4:56 PM
>>>>> To: dev@dpdk.org
>>>>> Cc: Xia, Chenbo <chenbo.xia@intel.com>; Pei, Andy
>> <andy.pei@intel.com>;
>>>>> kim.tae.kyung@navercorp.com; maxime.coquelin@redhat.com;
>> stable@dpdk.org;
>>>>> Wang, Xiao W <xiao.w.wang@intel.com>
>>>>> Subject: [PATCH v4] vdpa/ifc: fix update_datapath error handling
>>>>>
>>>>> Stop and return the error code when update_datapath fails.
>>>>> update_datapath prepares resources for the vdpa device.
>>>>> The driver should not perform any further actions
>>>>> if update_datapath returns an error.
>>>>>
>>>>> Fixes: a3f8150eac6d ("net/ifcvf: add ifcvf vDPA driver")
>>>>> Cc: stable@dpdk.org
>>>>>
>>>>> Signed-off-by: Taekyung Kim <kim.tae.kyung@navercorp.com>
>>>>> ---
>>>>> v4:
>>>>> * Add rte_vdpa_unregister_device in ifcvf_pci_probe
>>>>>
>>>>> v3:
>>>>> * Fix coding style
>>>>>
>>>>> v2:
>>>>> * Revert the prepared resources before returning an error
>>>>> * Rebase to 22.11 rc2
>>>>> * Add fixes and cc for backport
>>>>>
>>>>> ---
>>>>>    drivers/vdpa/ifc/ifcvf_vdpa.c | 27 +++++++++++++++++++++++----
>>>>>    1 file changed, 23 insertions(+), 4 deletions(-)
>>>>
>>>> I can't find your patch in patchwork:
>>>>
>>>>
>> http://patchwork.dpdk.org/project/dpdk/list/?series=&submitter=2877&sta
>> te=*&q=&archive=both&delegate=
>>>>
>>>> so it's difficult to review and merge. Do you know why or is it possible
>>>> that you send a new version to make it show on Patchwork today?
>>>>
>>>> Thanks,
>>>> Chenbo
>>>>
>>>
>>> Hi Chenbo,
>>>
>>> First, thanks for your review.
>>> I will send a new version for this patch soon.
>>>
>>> I think the mail for v4 is lost.
>>> Whenever I send a patch, I received "Your message to dev awaits
>> moderator approval"
>>> from dev-owner@dpdk.org with the reason "Post by non-member to a
>> members-only list".
>>> Maybe, the reason is that this is the first time that I submit a patch.
>>
>> No, I don't think subscription is needed, there should be another issue.
>> Ali & Thomas, any idea why it happens?
>>
> 
> Hello,
> 
> Subscription to the dev mailing list is required for posting without moderator approval.
> I see that Taekyung is a member only since Nov 08. Postings prior to his subscription are waiting moderation.

Ok, thanks. I did not know!

Maxime

> Thanks,
> Ali


  parent reply	other threads:[~2022-11-10  9:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <68eacb2c-4004-1f43-f14c-702bcec9fe6f@redhat.com>
2022-11-07  5:34 ` [PATCH v2] " Taekyung Kim
2022-11-07  8:59   ` [PATCH v3] " Taekyung Kim
2022-11-08  1:46     ` Xia, Chenbo
2022-11-08  7:30       ` Taekyung Kim
2022-11-08  7:39       ` Pei, Andy
2022-11-08  7:56         ` Xia, Chenbo
2022-11-08  8:27           ` Taekyung Kim
2022-11-08  8:56           ` [PATCH v4] " Taekyung Kim
2022-11-08 13:49             ` Maxime Coquelin
2022-11-09 10:45               ` Taekyung Kim
2022-11-09  2:39             ` Pei, Andy
2022-11-09 10:47               ` Taekyung Kim
2022-11-10  1:53             ` Xia, Chenbo
2022-11-10  4:02               ` Taekyung Kim
2022-11-10  9:20                 ` Maxime Coquelin
2022-11-10  9:34                   ` Ali Alnubani
2022-11-10  9:38                     ` David Marchand
2022-11-10  9:45                       ` Taekyung Kim
2022-11-10  9:42                     ` Maxime Coquelin [this message]
2022-11-10  4:09               ` [PATCH v5] " Taekyung Kim
2022-11-10  6:12                 ` Xia, Chenbo
2022-11-10  7:02                 ` Xia, Chenbo

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=529277ff-9e3e-15e9-d969-3fd68d66378e@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=andy.pei@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=kim.tae.kyung@navercorp.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xiao.w.wang@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;
as well as URLs for NNTP newsgroup(s).