From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>,
"Ruifeng.Wang@arm.com" <Ruifeng.Wang@arm.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v1] doc: arm64 cross docs improvements/fixes
Date: Fri, 26 Nov 2021 14:17:50 +0000 [thread overview]
Message-ID: <5b65cb2cc79f4c3883e4efd34de18e67@pantheon.tech> (raw)
In-Reply-To: <1965953.Lthp3rX6bU@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, November 26, 2021 2:54 PM
> To: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Cc: david.marchand@redhat.com; bruce.richardson@intel.com;
> Honnappa.Nagarahalli@arm.com; Ruifeng.Wang@arm.com;
> ferruh.yigit@intel.com; dev@dpdk.org
> Subject: Re: [PATCH v1] doc: arm64 cross docs improvements/fixes
>
> 18/11/2021 11:00, Juraj Linkeš:
> > Numactl cross compilation doesn't work with clang, remove it and fix
> > the gcc cross compiler executable name.
> >
> > Remove CFLAGS and LDFLAGS since Meson doesn't support them well enough.
> > Add alternatives.
> >
> > The names of the downloaded gcc binaries differ from those in cross
> > files, so point this out in docs.
> >
> > Fixes: eb0e12c0c299 ("doc: add clang to aarch64 cross build guide")
> >
> > Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> > ---
> > Let me know if I should split the patch.
>
> Yes, there are many things to discuss and review.
> Please split each concern in its own patch.
Will do.
> Anyway I cannot merge such patch without an Arm maintainer review.
>
Ok, I'll notify arm folks when I send the new version.
next prev parent reply other threads:[~2021-11-26 14:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 10:00 [PATCH v1] doc: arm64 cross docs improvements/fixes Juraj Linkeš
2021-11-26 13:53 ` Thomas Monjalon
2021-11-26 14:17 ` Juraj Linkeš [this message]
2021-12-07 11:05 ` [PATCH v2 0/4] " Juraj Linkeš
2021-12-07 11:05 ` [PATCH v2 1/4] doc: arm64 cross build CFLAGS/LDFLAGS alternatives Juraj Linkeš
2021-12-15 8:00 ` Ruifeng Wang
2021-12-07 11:05 ` [PATCH v2 2/4] doc: arm64 cross build binary names update Juraj Linkeš
2021-12-15 8:02 ` Ruifeng Wang
2021-12-07 11:05 ` [PATCH v2 3/4] doc: arm64 cross build numactl compilers Juraj Linkeš
2021-12-15 8:38 ` Ruifeng Wang
2021-12-07 11:05 ` [PATCH v2 4/4] docs: add an example arm64 cross file Juraj Linkeš
2021-12-15 8:59 ` Ruifeng Wang
2022-01-25 13:19 ` [PATCH v3 0/4] arm64 cross docs improvements/fixes Juraj Linkeš
2022-01-25 13:19 ` [PATCH v3 1/4] doc: arm64 cross build CFLAGS/LDFLAGS alternatives Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 2/4] doc: arm64 cross build binary names update Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 3/4] doc: arm64 cross build numactl compilers Juraj Linkeš
2022-01-25 13:20 ` [PATCH v3 4/4] doc: add an example arm64 cross file Juraj Linkeš
2022-03-16 19:19 ` [PATCH v3 0/4] arm64 cross docs improvements/fixes 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=5b65cb2cc79f4c3883e4efd34de18e67@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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 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.