DPDK patches and discussions
 help / color / mirror / Atom feed
From: Amiya Ranjan Mohakud <amiyaranjan.mohakud@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "Loftus, Ciara" <ciara.loftus@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH v2] net/iavf: fix VLAN offload strip flag
Date: Thu, 26 Jun 2025 10:04:00 +0530	[thread overview]
Message-ID: <CAL+mCpNm36+5Cc=4KLWdGjAOsgNGv+o4xUoMv86Fx7q9rPNngQ@mail.gmail.com> (raw)
In-Reply-To: <CAL+mCpOumEh6H8H6B9eLF=T-Hz6D8HwQOYCMjcAmpWVNS7JnPA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]

Just an additional note: It needs to be back ported to all LTS releases
till v22.11. Hope it will be taken care of.

Thanks
Amiya


On Thu, 26 Jun 2025 at 09:04, Amiya Ranjan Mohakud <
amiyaranjan.mohakud@gmail.com> wrote:

> Thanks Bruce and Ciara for the review/acceptance of the patch.
>
> Thanks
> Amiya
>
>
> On Wed, 25 Jun 2025 at 21:31, Bruce Richardson <bruce.richardson@intel.com>
> wrote:
>
>> On Wed, Jun 25, 2025 at 02:01:15PM +0000, Loftus, Ciara wrote:
>> > >
>> > > Thanks.
>> > >
>> > > Just wanted to know  - what are the next steps of the review and
>> approval
>> > > process?
>> > >
>> > > There is a test suite "ci/intel-Testing" failing now with v2 which
>> passed in v1. (
>> > > We know for sure, there is absolutely no code change between v1 and v2
>> > > except the commit message). Is there a way to trigger the test suite
>> again?
>> >
>> > Hi Amiya,
>> >
>> > There is no further action required on your end since the failure seems
>> like an issue with the test infrastructure. If the maintainer for the intel
>> next-net tree is happy with the patch they will pull it into the tree.
>> >
>> > Thanks,
>> > Ciara
>> >
>> Agree test failures look like false positives, as they are errors with the
>> PF driver and virtio driver, while this patch changes the VF driver.
>>
>> Patch applied to dpdk-next-net-intel.
>>
>> Thanks,
>> /Bruce
>>
>

[-- Attachment #2: Type: text/html, Size: 2788 bytes --]

  reply	other threads:[~2025-06-26  4:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-21  1:56 [PATCH] " Amiya Ranjan Mohakud
2025-06-23 10:57 ` Loftus, Ciara
2025-06-23 18:11 ` [PATCH v2] " Amiya Ranjan Mohakud
2025-06-23 18:50   ` Amiya Ranjan Mohakud
2025-06-24  9:19     ` Loftus, Ciara
2025-06-24 15:29       ` Amiya Ranjan Mohakud
2025-06-25 14:01         ` Loftus, Ciara
2025-06-25 16:00           ` Bruce Richardson
2025-06-26  3:34             ` Amiya Ranjan Mohakud
2025-06-26  4:34               ` Amiya Ranjan Mohakud [this message]
2025-06-24  9:19   ` Loftus, Ciara

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='CAL+mCpNm36+5Cc=4KLWdGjAOsgNGv+o4xUoMv86Fx7q9rPNngQ@mail.gmail.com' \
    --to=amiyaranjan.mohakud@gmail.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    /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).