From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Patil, Harish" <Harish.Patil@cavium.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] [18.02-rc2] net/qede: remove VF Tx switch option
Date: Fri, 12 Jan 2018 22:00:25 +0000 [thread overview]
Message-ID: <CY4PR0701MB38273F6E452AC5D7AA160A939F170@CY4PR0701MB3827.namprd07.prod.outlook.com> (raw)
In-Reply-To: <CY4PR0701MB3827D63984A86BC959D656AD9F160@CY4PR0701MB3827.namprd07.prod.outlook.com>
> From: Mody, Rasesh
> Sent: Thursday, January 11, 2018 11:03 AM
> To: 'Ferruh Yigit' <ferruh.yigit@intel.com>; Thomas Monjalon
> <thomas@monjalon.net>; Patil, Harish <Harish.Patil@cavium.com>
> Cc: dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH] [18.02-rc2] net/qede: remove VF Tx switch
> option
>
> Hi Ferruh,
>
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ferruh Yigit
> > Sent: Thursday, January 11, 2018 9:50 AM
> >
> > On 11/8/2017 12:41 AM, Thomas Monjalon wrote:
> > > The compile-time option CONFIG_RTE_LIBRTE_QEDE_VF_TX_SWITCH
> > > has been added just before the 17.11 release.
> > > Such new options are forbidden and must be replaced by a run-time
> > option.
> > > If it is not replaced in 18.02-rc1, this removal will be applied.
> >
> > I hope this is not forgotten!
>
> We'll submit this shortly.
Please check the patch link below that introduces a run-time driver option and replaces compile time option. It supersedes a patch, submitted by Thomas earlier, that only removes compile time option.
https://dpdk.org/dev/patchwork/patch/33696/
Thanks!
-Rasesh
prev parent reply other threads:[~2018-01-12 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 0:41 Thomas Monjalon
2018-01-11 17:50 ` Ferruh Yigit
2018-01-11 19:03 ` Mody, Rasesh
2018-01-12 22:00 ` Mody, Rasesh [this message]
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=CY4PR0701MB38273F6E452AC5D7AA160A939F170@CY4PR0701MB3827.namprd07.prod.outlook.com \
--to=rasesh.mody@cavium.com \
--cc=Harish.Patil@cavium.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).