From: Sunil Kumar Kori <sunil.kori@nxp.com>
To: Gowrishankar <gowrishankar.m@linux.vnet.ibm.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] event/dpaa: fix integer overflow on max_event_ports at compile time
Date: Fri, 13 Apr 2018 06:51:23 +0000 [thread overview]
Message-ID: <AM5PR0401MB2660D9E4D645A63007BEDC888FB30@AM5PR0401MB2660.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1103cd020ba0357f46650c6de1807cbf35d2a83c.1523595512.git.gowrishankar.m@linux.vnet.ibm.com>
> -----Original Message-----
> From: Gowrishankar [mailto:gowrishankar.m@linux.vnet.ibm.com]
> Sent: Friday, April 13, 2018 10:37 AM
> To: Sunil Kumar Kori <sunil.kori@nxp.com>; Shreyansh Jain
> <shreyansh.jain@nxp.com>
> Cc: Anatoly Burakov <anatoly.burakov@intel.com>; dev@dpdk.org; Thomas
> Monjalon <thomas@monjalon.net>; Gowrishankar Muthukrishnan
> <gowrishankar.m@linux.vnet.ibm.com>
> Subject: [PATCH] event/dpaa: fix integer overflow on max_event_ports at
> compile time
>
> From: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
>
> dev_info->max_event_ports is uint8_t. dpaa_event_dev_info_get assigns
> DPAA_EVENT_MAX_EVENT_PORT (which is RTE_MAX_LCORE, upto 256 in
> ppc64le) into this variable, which breaks compile in ppc64le.
>
> Fixes: 9caac5dd1e ("event/dpaa: introduce PMD")
>
> Signed-off-by: Gowrishankar Muthukrishnan
> <gowrishankar.m@linux.vnet.ibm.com>
>
Acked-by: Sunil Kumar Kori <sunil.kori@nxp.com>
next prev parent reply other threads:[~2018-04-13 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 5:06 Gowrishankar
2018-04-13 6:51 ` Sunil Kumar Kori [this message]
2018-04-16 14:45 ` Thomas Monjalon
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=AM5PR0401MB2660D9E4D645A63007BEDC888FB30@AM5PR0401MB2660.eurprd04.prod.outlook.com \
--to=sunil.kori@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=gowrishankar.m@linux.vnet.ibm.com \
--cc=shreyansh.jain@nxp.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).