From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>
Cc: pbhagavatula@marvell.com, jerinj@marvell.com, nd@arm.com,
Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org
Subject: Re: [PATCH v3 1/2] config/arm: allow WFE to be enabled config time
Date: Thu, 1 Feb 2024 22:07:36 +0530 [thread overview]
Message-ID: <CALBAE1NXFKzhnG7TMmLocYr6dkLgyDkqTOiUsAU8Cs0tj9QnMA@mail.gmail.com> (raw)
In-Reply-To: <4393fb53-2502-494b-b4cb-3b2a22e4aa1e@arm.com>
On Mon, Jan 22, 2024 at 12:13 PM Ruifeng Wang <Ruifeng.Wang@arm.com> wrote:
>
>
> On 2024/1/21 11:21 PM, pbhagavatula@marvell.com wrote:
> > From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> >
> > Allow RTE_ARM_USE_WFE to be enabled at meson configuration
> > time by passing it via c_args instead of modifying
> > `config/arm/meson.build`.
> >
> > Example usage:
> > meson build -Dc_args='-DRTE_ARM_USE_WFE' \
> > --cross-file config/arm/arm64_cn10k_linux_gcc
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Could you split and resend this series a two separate patch as this
patch needs to go through main tree.
next prev parent reply other threads:[~2024-02-01 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 19:36 [PATCH] event/cnxk: use WFE LDP loop for getwork routine pbhagavatula
2024-01-09 7:56 ` Jerin Jacob
2024-01-17 14:25 ` [PATCH v2 1/2] config/arm: allow WFE to be enabled config time pbhagavatula
2024-01-17 14:26 ` [PATCH v2 2/2] event/cnxk: use WFE LDP loop for getwork routine pbhagavatula
2024-01-18 1:52 ` [PATCH v2 1/2] config/arm: allow WFE to be enabled config time Ruifeng Wang
2024-01-21 15:21 ` [PATCH v3 " pbhagavatula
2024-01-21 15:21 ` [PATCH v3 2/2] event/cnxk: use WFE LDP loop for getwork routine pbhagavatula
2024-01-22 6:37 ` [PATCH v3 1/2] config/arm: allow WFE to be enabled config time fengchengwen
2024-01-22 6:43 ` Ruifeng Wang
2024-02-01 16:37 ` Jerin Jacob [this message]
2024-02-01 22:03 ` [PATCH v4] event/cnxk: use WFE LDP loop for getwork routine pbhagavatula
2024-02-25 15:20 ` Jerin Jacob
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=CALBAE1NXFKzhnG7TMmLocYr6dkLgyDkqTOiUsAU8Cs0tj9QnMA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=pbhagavatula@marvell.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).