From: Thomas Monjalon <thomas@monjalon.net>
To: Phil Yang <phil.yang@arm.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, jerinj@marvell.com,
Honnappa.Nagarahalli@arm.com, gavin.hu@arm.com,
joyce.kong@arm.com, nd@arm.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: add aarch32 build guidance
Date: Sun, 24 May 2020 23:21:18 +0200 [thread overview]
Message-ID: <4358338.8uJDUzQGum@thomas> (raw)
In-Reply-To: <1573468461-25972-2-git-send-email-phil.yang@arm.com>
11/11/2019 11:34, Phil Yang:
> Add a guidance for aarch64 natively build 32-bit aarch32 DPDK.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Phil Yang <phil.yang@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> Tested-by: Joyce Kong <joyce.kong@arm.com>
>
> ---
> .../linux_gsg/cross_build_dpdk_for_arm64.rst | 36 ++++++++++++++++++----
> 1 file changed, 30 insertions(+), 6 deletions(-)
What is the status of this patch?
The patch 1/2 was rejected.
There are new works around aarch32.
Is it still relevant?
next prev parent reply other threads:[~2020-05-24 21:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 10:34 [dpdk-dev] [PATCH 1/2] mk: fix unsupported flag error on armhf architercture Phil Yang
2019-11-11 10:34 ` [dpdk-dev] [PATCH 2/2] doc: add aarch32 build guidance Phil Yang
2020-05-24 21:21 ` Thomas Monjalon [this message]
2020-05-25 3:20 ` Phil Yang
2020-05-27 8:28 ` Ruifeng Wang
2020-07-02 5:37 ` Phil Yang
2020-07-02 8:01 ` Jerin Jacob
2019-11-11 10:47 ` [dpdk-dev] [PATCH 1/2] mk: fix unsupported flag error on armhf architercture Bruce Richardson
2019-11-12 5:25 ` Phil Yang (Arm Technology China)
2019-11-12 6:03 ` Thomas Monjalon
2019-11-12 6:40 ` Phil Yang (Arm Technology China)
2019-11-26 17:01 ` Thomas Monjalon
2019-11-27 8:09 ` Phil Yang (Arm Technology China)
2019-11-27 9:29 ` Bruce Richardson
2019-11-27 10:00 ` Phil Yang (Arm Technology China)
2019-11-27 10:32 ` 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=4358338.8uJDUzQGum@thomas \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=jerinj@marvell.com \
--cc=joyce.kong@arm.com \
--cc=nd@arm.com \
--cc=phil.yang@arm.com \
--cc=stable@dpdk.org \
/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).