From: Thomas Monjalon <thomas@monjalon.net>
To: Chandrakant Sharpa <s.chandrakant@globaledgesoft.com>
Cc: dev@dpdk.org, zaheer.rm@globaledgesoft.com,
gurusidhesh.gh@globaledgesoft.com, sm.supriya@globaledgesoft.com,
david.marchand@redhat.com, bruce.richardson@intel.com,
Jan Viktorin <viktorin@rehivetech.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Jerin Jacob <jerinj@marvell.com>,
honnappa.nagarahalli@arm.com
Subject: Re: [dpdk-dev] [PATCH] Add Armv7 support
Date: Thu, 17 Jun 2021 09:51:44 +0200 [thread overview]
Message-ID: <2086868.Y7UdBn2X1H@thomas> (raw)
In-Reply-To: <20210610111839.7481-1-s.chandrakant@globaledgesoft.com>
10/06/2021 13:18, s.chandrakant@globaledgesoft.com:
> From: Chandrakant Sharpa <s.chandrakant@globaledgesoft.com>
>
> Adding support for Armv7 based platforms.
> Used latest GNU cross compiler toolchain
> version(10.2) for testing.
>
> Signed-off-by: Chandrakant Sharpa <s.chandrakant@globaledgesoft.com>
> ---
> config/arm/arm_armv7a_linux_gcc | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
Adding maintainers.
Note: Armv7 is/was supported but was missing in the meson build system.
How compilation is looking? I guess there are tons of warnings?
next prev parent reply other threads:[~2021-06-17 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 11:18 [dpdk-dev] [PATCH] Add Armv7 support s.chandrakant
2021-06-17 7:51 ` Thomas Monjalon [this message]
2021-06-18 6:19 ` Supriya Shekhar Mane
2021-06-23 6:35 ` Ruifeng Wang
2021-06-24 6:21 ` Supriya Shekhar Mane
2021-06-24 6:58 ` Ruifeng Wang
2023-07-17 16:50 ` Stephen Hemminger
2023-07-18 3:22 ` Ruifeng Wang
2021-11-16 12:13 ` Juraj Linkeš
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=2086868.Y7UdBn2X1H@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gurusidhesh.gh@globaledgesoft.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=ruifeng.wang@arm.com \
--cc=s.chandrakant@globaledgesoft.com \
--cc=sm.supriya@globaledgesoft.com \
--cc=viktorin@rehivetech.com \
--cc=zaheer.rm@globaledgesoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.