From: fengchengwen <fengchengwen@huawei.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <datshan@qq.com>, <thomas@monjalon.net>, <dev@dpdk.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH 0/2] fix dmadev incomplete ABI validation
Date: Thu, 2 Jul 2026 20:50:41 +0800 [thread overview]
Message-ID: <f417556a-1a6a-408a-babd-6569ca9602e2@huawei.com> (raw)
In-Reply-To: <CAJFAV8ytRF4jjsM=Euoij3=76BgRCCZPk-7MX7iCWv4zetz6yg@mail.gmail.com>
On 7/2/2026 2:52 PM, David Marchand wrote:
> On Thu, 2 Jul 2026 at 03:35, fengchengwen <fengchengwen@huawei.com> wrote:
>>
>> On 7/2/2026 1:01 AM, David Marchand wrote:
>>> On Wed, 1 Jul 2026 at 10:11, David Marchand <david.marchand@redhat.com> wrote:
>>>> On Tue, 30 Jun 2026 at 15:24, <datshan@qq.com> wrote:
>>>>>
>>>>> From: datshan <datshan@qq.com>
>>>>>
>>>>> Fix dmadev incomplete ABI validation.
>>>>>
>>>>> Chengwen Feng (2):
>>>>> dmadev: fix incomplete configuration validation
>>>>> test/dmadev: add config and vchan validation tests
>>>>>
>>>>> app/test/test_dmadev_api.c | 186 ++++++++++++++++++++++++++++++++++---
>>>>> lib/dmadev/rte_dmadev.c | 156 +++++++++++++++++++++----------
>>>>> 2 files changed, 283 insertions(+), 59 deletions(-)
>>>>>
>>>>
>>>> This series is not versionned, but I guess this is a new revision.
>>>> Don't forget to flag your submissions with a version number in the future.
>>>> I marked the previous patches as superseded in patchwork.
>>>>
>>>> Also provide a high level summary of the differences between versions.
>>>>
>>>> All of those steps are listed in the contributing guide, I suggest
>>>> (re-)reading the whole guide, with a highlight on:
>>>> https://doc.dpdk.org/guides/contributing/patches.html#steps-to-getting-your-patch-merged
>>>>
>>>> Thanks, I'll try to find some time to review this week.
>>>
>>> Well, enforcing *now* that some fields are 0 is actually breaking ABI
>>> for existing applications.
>>> This change should be deferred to 26.11, and backporting to a LTS is
>>> not possible.
>>
>> OK
>> BTW: Should I submit another version in 26.11 cycle or do nothing?
>
> I'll mark those patches as Deferred in patchwork.
> That's enough, I will apply them after 26.11-rc0.
Thanks
>
>
next prev parent reply other threads:[~2026-07-02 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 4:17 [PATCH 0/2] fix dmadev incomplete ABI validation datshan
2026-07-01 8:11 ` David Marchand
2026-07-01 17:01 ` David Marchand
2026-07-02 1:35 ` fengchengwen
2026-07-02 6:52 ` David Marchand
2026-07-02 12:50 ` fengchengwen [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-29 6:19 datshan
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=f417556a-1a6a-408a-babd-6569ca9602e2@huawei.com \
--to=fengchengwen@huawei.com \
--cc=bruce.richardson@intel.com \
--cc=datshan@qq.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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