From: Christoph Hellwig <hch@infradead.org>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-riscv@lists.infradead.org,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, Albert Ou <aou@eecs.berkeley.edu>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH] riscv: add arch/riscv/Kbuild
Date: Mon, 26 Aug 2019 04:35:26 -0700 [thread overview]
Message-ID: <20190826113526.GA23425@infradead.org> (raw)
In-Reply-To: <20190821092658.32764-1-yamada.masahiro@socionext.com>
On Wed, Aug 21, 2019 at 06:26:58PM +0900, Masahiro Yamada wrote:
> Use the standard obj-y form to specify the sub-directories under
> arch/riscv/. No functional change intended.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Do you have a document what the grand scheme here is? Less of the magic
in arch/$(ARCH)/Makefile sounds like a good idea, but unless we have
a very specific split between the kbuild makefile and various override
I fear just splitting things up into two files doesn't really help much.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-08-26 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 9:26 [PATCH] riscv: add arch/riscv/Kbuild Masahiro Yamada
2019-08-26 11:35 ` Christoph Hellwig [this message]
2019-08-27 5:14 ` Masahiro Yamada
2019-08-30 15:53 ` Christoph Hellwig
2019-08-31 13:04 ` Masahiro Yamada
2019-09-02 7:42 ` Christoph Hellwig
2019-09-03 14:31 ` Masahiro Yamada
2019-08-31 0:51 ` Paul Walmsley
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=20190826113526.GA23425@infradead.org \
--to=hch@infradead.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).