From: Luca Boccassi <bluca@debian.org>
To: Vivek Sharma <vivek.sharma@caviumnetworks.com>,
santosh.shukla@cavium.com
Cc: vivek.sharma@cavium.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v1] eal: use correct data type for slab operations
Date: Tue, 25 Sep 2018 13:38:09 +0100 [thread overview]
Message-ID: <1537879089.10481.49.camel@debian.org> (raw)
In-Reply-To: <1537803523-23347-1-git-send-email-vivek.sharma@caviumnetworks.com>
On Mon, 2018-09-24 at 21:08 +0530, Vivek Sharma wrote:
> Currently, slab operations use unsigned long data type for 64-bit
> slab
> related operations. On target 'i686-native-linuxapp-gcc', unsigned
> long
> is 32-bit and thus, slab operations breaks on this target. Changing
> slab
> operations to use unsigned long long for correct functioning on all
> targets.
>
> Fixes: de3cfa2c9823 ("sched: initial import")
> Fixes: 693f715da45c ("remove extra parentheses in return statement")
> CC: stable@dpdk.org
>
> Signed-off-by: Vivek Sharma <vivek.sharma@caviumnetworks.com>
> ---
> lib/librte_eal/common/include/rte_bitmap.h | 14 +++++++-------
> test/test/test_bitmap.c | 18 ++++++++++++++++++
> 2 files changed, 25 insertions(+), 7 deletions(-)
Hi,
Is this patch only for stable releases? If so, which one? Or was dev@
absent by mistake?
Thanks
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2018-09-25 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 15:38 Vivek Sharma
2018-09-24 15:50 ` Vivek Sharma
2018-09-24 17:12 ` Dumitrescu, Cristian
2018-10-08 15:57 ` Dumitrescu, Cristian
2018-09-25 9:53 ` [dpdk-stable] [PATCH v2] eal: use correct data type for bitmap " Vivek Sharma
2018-09-25 12:38 ` Luca Boccassi [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=1537879089.10481.49.camel@debian.org \
--to=bluca@debian.org \
--cc=santosh.shukla@cavium.com \
--cc=stable@dpdk.org \
--cc=vivek.sharma@cavium.com \
--cc=vivek.sharma@caviumnetworks.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).