From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] patchset for bnxt PMD
Date: Tue, 12 Oct 2021 13:30:30 -0700 [thread overview]
Message-ID: <CACZ4nhuS39DgU8GBgyeqW5_MqUw+T0s2USzUtSv2uOMjO8Kj_Q@mail.gmail.com> (raw)
In-Reply-To: <dbe8f02f-461a-0806-923d-122d23ee6cac@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]
On Tue, Oct 12, 2021 at 12:49 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> On 10/12/2021 8:03 PM, Ajit Khaparde wrote:
> > On Tue, Oct 12, 2021 at 11:16 AM Ajit Khaparde
> > <ajit.khaparde@broadcom.com> wrote:
> >>
> >> On Tue, Oct 12, 2021 at 11:14 AM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> >>>
> >>> On 10/7/2021 5:54 PM, Ajit Khaparde wrote:
> >>>> On Wed, Oct 6, 2021 at 8:23 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
> >>>> wrote:
> >>>>
> >>>>> Apart from fixing an issue with Rx queue state at startup,
> >>>>> this patchset enhances support for RSS action and
> >>>>> optimizes the mbuf requirement at startup by creating the
> >>>>> aggregation rings only when needed (rx_scatter is enabled).
> >>>>>
> >>>>> Please apply!
> >>>>>
> >>>> Patchset applied to dpdk-next-net-brcm.
> >>>>
> >>>>
> >>>
> >>> Hi Ajit,
> >>>
> >>> dpdk-next-net-brcm conflicts with next-net because of some patches
> >>> updating bnxt in next-net.
> >>> Can you please rebase 'dpdk-next-net-brcm' on top of latest next-net?
> >> Sure. I will send an email once it's ready.
> > Done. I have rebased the repo to the latest next-net/main
> > and merged the patches. Please try now.
> >
>
> Hi Ajit,
>
> I am getting lots of checkpatch warnings on the patches in your tree,
> but I don't see them in the patchwork. Warnings can be because of the
> updates during rebase.
>
> If there is code change during rebase, to not have a diverge between
> the patch in the patchwork and what we are merging, can you please send
> and updated version of the effected patches first?
There is no code change made during the rebase.
My checkpatch run did not point out anything.
But let me try again. Thanks Ferruh.
Thanks
Ajit
> This lets us see the CI results and later they can be merge in your tree
> again.
>
next prev parent reply other threads:[~2021-10-12 20:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 3:23 Ajit Khaparde
2021-10-07 3:23 ` [dpdk-dev] [PATCH 1/3] net/bnxt: create aggregration rings when needed Ajit Khaparde
2021-10-07 3:23 ` [dpdk-dev] [PATCH 2/3] net/bnxt: fix Rx queue state on start Ajit Khaparde
2021-10-07 3:23 ` [dpdk-dev] [PATCH 3/3] net/bnxt: enhance support for RSS action Ajit Khaparde
2021-10-07 16:54 ` [dpdk-dev] [PATCH 0/3] patchset for bnxt PMD Ajit Khaparde
2021-10-12 18:14 ` Ferruh Yigit
2021-10-12 18:16 ` Ajit Khaparde
2021-10-12 19:03 ` Ajit Khaparde
2021-10-12 19:49 ` Ferruh Yigit
2021-10-12 20:30 ` Ajit Khaparde [this message]
2021-10-12 20:39 ` Ajit Khaparde
2021-10-12 21:14 ` [dpdk-dev] [PATCH v3 " Ajit Khaparde
2021-10-12 21:14 ` [dpdk-dev] [PATCH v3 1/3] net/bnxt: create aggregration rings when needed Ajit Khaparde
2021-10-12 21:14 ` [dpdk-dev] [PATCH v3 2/3] net/bnxt: fix Rx queue state on start Ajit Khaparde
2021-10-12 21:14 ` [dpdk-dev] [PATCH v3 3/3] net/bnxt: enhance support for RSS action Ajit Khaparde
2021-10-12 21:18 ` [dpdk-dev] [PATCH v4 0/3] patchset for bnxt PMD Ajit Khaparde
2021-10-12 21:18 ` [dpdk-dev] [PATCH v4 1/3] net/bnxt: create aggregration rings when needed Ajit Khaparde
2021-10-12 21:18 ` [dpdk-dev] [PATCH v4 2/3] net/bnxt: fix Rx queue state on start Ajit Khaparde
2021-10-12 21:18 ` [dpdk-dev] [PATCH v4 3/3] net/bnxt: enhance support for RSS action Ajit Khaparde
2021-10-12 21:47 ` [dpdk-dev] [PATCH v4 0/3] patchset for bnxt PMD Ferruh Yigit
-- strict thread matches above, loose matches on Subject: below --
2020-09-29 20:59 [dpdk-dev] [PATCH " Ajit Khaparde
2020-09-30 17:16 ` Ajit Khaparde
2020-09-30 21:29 ` Ajit Khaparde
2017-10-12 17:35 Ajit Khaparde
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=CACZ4nhuS39DgU8GBgyeqW5_MqUw+T0s2USzUtSv2uOMjO8Kj_Q@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).