All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Kardach <kda@semihalf.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Stanislaw Kardach <kda@semihalf.com>,
	dev@dpdk.org, upstream@semihalf.com
Subject: [PATCH] config/riscv: name the cross file properly
Date: Tue, 21 Jun 2022 14:29:23 +0200	[thread overview]
Message-ID: <20220621122923.188425-1-kda@semihalf.com> (raw)

Since the riscv64_linux_gcc was in fact a Ubuntu-specific cross-file,
rename it.

Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
---
 .ci/linux-build.sh                                           | 2 +-
 config/riscv/{riscv64_linux_gcc => riscv64_linux_gcc_ubuntu} | 0
 devtools/test-meson-builds.sh                                | 2 +-
 doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst          | 4 ++--
 4 files changed, 4 insertions(+), 4 deletions(-)
 rename config/riscv/{riscv64_linux_gcc => riscv64_linux_gcc_ubuntu} (100%)

diff --git a/.ci/linux-build.sh b/.ci/linux-build.sh
index 06104eca22..dcf4d4ccb3 100755
--- a/.ci/linux-build.sh
+++ b/.ci/linux-build.sh
@@ -75,7 +75,7 @@ if [ "$PPC64LE" = "true" ]; then
 fi
 
 if [ "$RISCV64" = "true" ]; then
-    cross_file=config/riscv/riscv64_linux_gcc
+    cross_file=config/riscv/riscv64_linux_gcc_ubuntu
 fi
 
 if [ -n "$cross_file" ]; then
diff --git a/config/riscv/riscv64_linux_gcc b/config/riscv/riscv64_linux_gcc_ubuntu
similarity index 100%
rename from config/riscv/riscv64_linux_gcc
rename to config/riscv/riscv64_linux_gcc_ubuntu
diff --git a/devtools/test-meson-builds.sh b/devtools/test-meson-builds.sh
index 04a85fe987..00b97a3e50 100755
--- a/devtools/test-meson-builds.sh
+++ b/devtools/test-meson-builds.sh
@@ -265,7 +265,7 @@ f=$srcdir/config/ppc/ppc64le-power8-linux-gcc
 build build-ppc64-power8-gcc $f ABI $use_shared
 
 # generic RISC-V
-f=$srcdir/config/riscv/riscv64_linux_gcc
+f=$srcdir/config/riscv/riscv64_linux_gcc_ubuntu
 build build-riscv64-generic-gcc $f ABI $use_shared
 
 # Test installation of the x86-generic target, to be used for checking
diff --git a/doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst b/doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst
index 9e121645a8..84d1ea3aa6 100644
--- a/doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst
+++ b/doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst
@@ -74,7 +74,7 @@ To cross-compile DPDK for a desired target machine use the following command::
 For example if the target machine is a generic rv64gc RISC-V, use the following
 command::
 
-   meson riscv64-build-gcc --cross-file config/riscv/riscv64_linux_gcc
+   meson riscv64-build-gcc --cross-file config/riscv/riscv64_linux_gcc_ubuntu
    ninja -C riscv64-build-gcc
 
 If riscv-gnu-toolchain is used, binary names should be updated to match. Update
@@ -106,7 +106,7 @@ Supported cross-compilation targets
 
 Currently the following targets are supported:
 
-* Generic rv64gc ISA: ``config/riscv/riscv64_linux_gcc``
+* Generic rv64gc ISA: ``config/riscv/riscv64_linux_gcc_ubuntu``
 
 * SiFive U740 SoC: ``config/riscv/riscv64_sifive_u740_linux_gcc``
 
-- 
2.30.2

             reply	other threads:[~2022-06-21 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 12:29 Stanislaw Kardach [this message]
2024-10-02 16:51 ` [PATCH] config/riscv: name the cross file properly Stephen Hemminger
2024-10-03 11:44   ` Radoslaw Biernacki
2024-10-15 11:34     ` Stanisław Kardach

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=20220621122923.188425-1-kda@semihalf.com \
    --to=kda@semihalf.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=upstream@semihalf.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.