Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 3 Aug 2018 00:39:16 -0700
From:   Christoph Hellwig <hch@infradead.org>
To:     Palmer Dabbelt <palmer@sifive.com>
Cc:     deepa.kernel@gmail.com, zongbox@gmail.com, y2038@lists.linaro.org,
        tglx@linutronix.de, linux-riscv@lists.infradead.org,
        linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v3 3/7] riscv: Delete asm/compat.h
Message-ID: <20180803073916.GA19580@infradead.org>
References: <20180707054247.19802-4-deepa.kernel@gmail.com>
 <mhng-ca3e24c4-d59b-491d-a9c5-c8466168b638@palmer-si-x1c4>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <mhng-ca3e24c4-d59b-491d-a9c5-c8466168b638@palmer-si-x1c4>
User-Agent: Mutt/1.9.2 (2017-12-15)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Aug 02, 2018 at 06:26:58PM -0700, Palmer Dabbelt wrote:
> I thought we were using this to make uname print "riscv64" (or "riscv32")
> instead of just "riscv"?  Is there another mechanism to do that?

That is set in the UTS_MACHINE variable in arch/riscv/Makefile
and doesn't involve compat.h at all except when actually implementing
32-bit compat on 64 bit, which RISC-V doesn't (at least yet).