From: "Jiang, YuX" <yux.jiang@intel.com>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Liang, LongfengX" <longfengx.liang@intel.com>,
"Singh, Aman Deep" <aman.deep.singh@intel.com>
Subject: RE: [20.11] kni: fix build for SLES15-SP3
Date: Thu, 9 Dec 2021 03:26:04 +0000 [thread overview]
Message-ID: <BYAPR11MB27110B5509D1C5B999BB3AA1FE709@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <b59873b474db8bc3869758be36e335f0213017f1.camel@nvidia.com>
> -----Original Message-----
> From: Xueming(Steven) Li <xuemingl@nvidia.com>
> Sent: Wednesday, December 8, 2021 6:59 PM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>
> Cc: stable@dpdk.org; Liang, LongfengX <longfengx.liang@intel.com>; Jiang,
> YuX <yux.jiang@intel.com>; Singh, Aman Deep
> <aman.deep.singh@intel.com>
> Subject: Re: [20.11] kni: fix build for SLES15-SP3
>
> On Wed, 2021-12-08 at 10:37 +0000, Ferruh Yigit wrote:
> > On 12/8/2021 10:34 AM, Ferruh Yigit wrote:
> > > From: Aman Singh <aman.deep.singh@intel.com>
> > >
> > > [ upstream commit c28e2165ec360c39ea0e3a0c02b4229966697384 ]
> > >
> > > As suse version numbering is inconsistent to determine Linux kernel
> > > API to be used. In this patch we check parameter of 'ndo_tx_timeout'
> > > API directly from the kernel source. This is done only for suse build.
> > >
> > > Bugzilla ID: 812
> > > Cc: stable@dpdk.org
> > >
> > > Signed-off-by: Aman Singh <aman.deep.singh@intel.com>
> > > Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
> > > Tested-by: Longfeng Liang <longfengx.liang@intel.com>
> > > ---
> > > Cc: yux.jiang@intel.com
> > >
> > > @Yu, can you please test the patch on SLES15-SP3, I am sending the
> > > backport without testing it on SUSE.
> >
> > Hi Xueming(Steven),
> >
> > Can you please consider this build fix for -rc2 when Yu verifies it?
>
> NP, noted.
>
Tested-by: Longfeng Liang <longfengx.liang@intel.com>
Verify the patch passed on OpenSuse15.3 with gcc7.5.0&clang11.0.1
DPDK: DPDK20.11.4-rc1
prev parent reply other threads:[~2021-12-09 3:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 10:34 Ferruh Yigit
2021-12-08 10:37 ` Ferruh Yigit
2021-12-08 10:58 ` Xueming(Steven) Li
2021-12-09 3:26 ` Jiang, YuX [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=BYAPR11MB27110B5509D1C5B999BB3AA1FE709@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=aman.deep.singh@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=longfengx.liang@intel.com \
--cc=stable@dpdk.org \
--cc=xuemingl@nvidia.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).