From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: Haiyue Wang <haiyue.wang@intel.com>, dpdk-dev <dev@dpdk.org>,
Jerin Jacob <jerinj@marvell.com>, Gavin Hu <gavin.hu@arm.com>,
Matan Azrad <matan@mellanox.com>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] eal: fix structure marker 4B type error
Date: Mon, 9 Mar 2020 10:37:25 +0530 [thread overview]
Message-ID: <CALBAE1PiUx0qxJ5qt7s4Fi1j6d7kkbyYJv9r70XTMgr8oW5=Zg@mail.gmail.com> (raw)
In-Reply-To: <20200308052459.GD18727@intel.com>
On Sun, Mar 8, 2020 at 10:57 AM Ye Xiaolong <xiaolong.ye@intel.com> wrote:
>
> On 03/08, Haiyue Wang wrote:
> >Use the 32bit typedef for structure 4B alignment marking.
> >
> >Fixes: 2b393160a480 ("eal: introduce structure markers")
> >Cc: stable@dpdk.org
> >
> >Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
> >---
> > lib/librte_eal/common/include/rte_common.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/lib/librte_eal/common/include/rte_common.h b/lib/librte_eal/common/include/rte_common.h
> >index 4b5f3a31f..3662545d2 100644
> >--- a/lib/librte_eal/common/include/rte_common.h
> >+++ b/lib/librte_eal/common/include/rte_common.h
> >@@ -344,7 +344,7 @@ __extension__ typedef uint8_t RTE_MARKER8[0];
> > /** Marker for 2B alignment in a structure. */
> > __extension__ typedef uint16_t RTE_MARKER16[0];
> > /** Marker for 4B alignment in a structure. */
> >-__extension__ typedef uint16_t RTE_MARKER32[0];
> >+__extension__ typedef uint32_t RTE_MARKER32[0];
> > /** Marker for 8B alignment in a structure. */
> > __extension__ typedef uint64_t RTE_MARKER64[0];
> >
> >--
> >2.25.1
> >
>
> Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>
Acked-by: Jerin Jacob <jerinj@marvell.com>
next prev parent reply other threads:[~2020-03-09 5:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 4:18 Haiyue Wang
2020-03-08 5:24 ` Ye Xiaolong
2020-03-09 5:07 ` Jerin Jacob [this message]
2020-03-13 9:43 ` David Marchand
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='CALBAE1PiUx0qxJ5qt7s4Fi1j6d7kkbyYJv9r70XTMgr8oW5=Zg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=haiyue.wang@intel.com \
--cc=jerinj@marvell.com \
--cc=matan@mellanox.com \
--cc=stable@dpdk.org \
--cc=xiaolong.ye@intel.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).