From: Christoph Hellwig <hch@lst.de>
To: Borislav Petkov <bp@alien8.de>
Cc: tony.luck@intel.com, yash.shah@sifive.com, rrichter@marvell.com,
james.morse@arm.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, linux-riscv@lists.infradead.org,
mchehab@kernel.org, Christoph Hellwig <hch@lst.de>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH, resend] riscv: move sifive_l2_cache.c to drivers/soc
Date: Thu, 7 Nov 2019 10:19:25 +0100 [thread overview]
Message-ID: <20191107091925.GA10676@lst.de> (raw)
In-Reply-To: <20191106150259.GB28380@zn.tnic>
On Wed, Nov 06, 2019 at 04:02:59PM +0100, Borislav Petkov wrote:
> On Wed, Nov 06, 2019 at 03:48:59PM +0100, Christoph Hellwig wrote:
> > On Wed, Nov 06, 2019 at 10:10:13AM +0100, Borislav Petkov wrote:
> > > Also, building with a cross-compiler fails here:
> >
> > What config? riscv defconfig + CONFIG_SIFIVE_L2 works just fine for me.
>
> Do you not see the one I attached?
Sorry, missed it.
The problem is that you have a modular build, which doesn't make much
sense given that the actual EDAC_SIFIVE needs to be built-in anyway.
I've changed it to bool and will resend.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-11-07 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 1:17 [PATCH, resend] riscv: move sifive_l2_cache.c to drivers/soc Christoph Hellwig
2019-11-06 9:10 ` Borislav Petkov
2019-11-06 14:48 ` Christoph Hellwig
2019-11-06 15:02 ` Borislav Petkov
2019-11-07 9:19 ` Christoph Hellwig [this message]
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=20191107091925.GA10676@lst.de \
--to=hch@lst.de \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rrichter@marvell.com \
--cc=tony.luck@intel.com \
--cc=yash.shah@sifive.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).