From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
David Marchand <david.marchand@redhat.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>,
Thierry Herbelot <thierry.herbelot@6wind.com>, dev <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix compilation error on Redhat 8
Date: Sun, 20 Sep 2020 15:26:10 +0000 [thread overview]
Message-ID: <MN2PR11MB4063857BE28546B7E6834A259C3D0@MN2PR11MB4063.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CACZ4nhtUq03SD=4-oOhy89vLoNk_+oxfT-st455G5ErYYC1iqA@mail.gmail.com>
Hi, David & Ajit
Yes, I will submit a patch to change all eth port id to uint16_t
this week as I promised. Is this ok for you?
Thanks,
Chenbo
> -----Original Message-----
> From: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Sent: Saturday, September 19, 2020 12:16 AM
> To: David Marchand <david.marchand@redhat.com>
> Cc: Somnath Kotur <somnath.kotur@broadcom.com>; Thierry Herbelot
> <thierry.herbelot@6wind.com>; Xia, Chenbo <chenbo.xia@intel.com>; dev
> <dev@dpdk.org>; Thomas Monjalon <thomas@monjalon.net>
> Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix compilation error on Redhat
> 8
>
> ::snip::
> > >
> >
> > This patch rang a bell.
> > There is the exact same patch proposed by Xia with a comment, so I
> > guess Xia is still working on it?
> > https://patchwork.dpdk.org/patch/75177/#117201
> Xia,
> Will you submit the changes that Thomas asked for?
> Otherwise I will apply the bnxt patch and you can work on the rest.
>
> Thanks
> Ajit
prev parent reply other threads:[~2020-09-20 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 7:01 Thierry Herbelot
2020-09-18 7:12 ` Somnath Kotur
2020-09-18 7:31 ` David Marchand
2020-09-18 16:16 ` Ajit Khaparde
2020-09-20 15:26 ` Xia, Chenbo [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=MN2PR11MB4063857BE28546B7E6834A259C3D0@MN2PR11MB4063.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=somnath.kotur@broadcom.com \
--cc=thierry.herbelot@6wind.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).