public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Westover <kwestover.kw@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH] riscv: Set SRCARCH to riscv if ARCH is riscv64 or riscv32
Date: Wed, 30 Mar 2022 14:40:01 -0400	[thread overview]
Message-ID: <e55edf6f-2aac-87a5-c0f8-363a536b9f92@gmail.com> (raw)
In-Reply-To: <CAK7LNASxaJMUAS6vgcDX3jwM9LQj7Lz8RX941FQhrDrtJSt6GA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 768 bytes --]

Hello Masahiro,

On 3/30/22 11:31 AM, Masahiro Yamada wrote:
> On Wed, Mar 30, 2022 at 11:34 PM Ben Westover <kwestover.kw@gmail.com> wrote:
>>
>> When riscv64 or riscv32 are used as the value for ARCH during compilation, like
>> in tools that get the ARCH value from uname, set SRCARCH to riscv instead of
>> failing because the riscv64 and riscv32 targets don't exist.
> 
> Can you refer to the code that really needs this?
Some software like DKMS compiles out-of-tree modules by running `uname -m`and
using that for the ARCH value. Without this patch, that compilation fails because
uname shows either riscv64 or riscv32 while riscv should be used.
This code already exists for sparc and parisc, as well as x86 of course.

Thanks,
--
Ben Westover

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2022-03-30 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 14:34 [PATCH] riscv: Set SRCARCH to riscv if ARCH is riscv64 or riscv32 Ben Westover
2022-03-30 15:31 ` Masahiro Yamada
2022-03-30 18:40   ` Ben Westover [this message]
2022-03-31  1:34     ` Masahiro Yamada
2022-03-31  2:16       ` Ben Westover

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=e55edf6f-2aac-87a5-c0f8-363a536b9f92@gmail.com \
    --to=kwestover.kw@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=ndesaulniers@google.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