From: Paul Walmsley <paul.walmsley@sifive.com>
To: Yash Shah <yash.shah@sifive.com>
Cc: linux-riscv@lists.infradead.org, linux-edac@vger.kernel.org,
palmer@sifive.com, paul.walmsley@sifive.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, aou@eecs.berkeley.edu, bp@alien8.de,
mchehab@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] L2 Cache EDAC Support for HiFive Unleashed
Date: Tue, 12 Mar 2019 09:32:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1903120925400.26459@viisi.sifive.com> (raw)
In-Reply-To: <1552382461-13051-1-git-send-email-yash.shah@sifive.com>
Hello Yash,
On Tue, 12 Mar 2019, Yash Shah wrote:
> This patch series adds a L2 Cache EDAC driver and DT documentation
> for HiFive Unleashed board.
This should also reference the "FU540-C000 chip" since there isn't
anything board-specific about it.
Also - could you please describe in your patch 0 message what kernel
commit this driver has been tested on; or, if it's not a mainline commit,
what additional patches are needed to test it?
thanks,
- Paul
prev parent reply other threads:[~2019-03-12 16:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 9:20 [PATCH 0/2] L2 Cache EDAC Support for HiFive Unleashed Yash Shah
2019-03-12 9:21 ` [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller Yash Shah
2019-03-28 13:16 ` Rob Herring
2019-03-28 18:47 ` James Morse
2019-03-29 14:11 ` Rob Herring
2019-03-29 14:27 ` Borislav Petkov
2019-03-29 19:41 ` Rob Herring
2019-03-29 20:24 ` Borislav Petkov
2019-04-04 1:04 ` Rob Herring
2019-04-01 16:36 ` James Morse
2019-04-04 1:17 ` Rob Herring
2019-03-12 9:21 ` [PATCH 2/2] sifive: edac: Add EDAC driver for Sifive l2 Cache Controller Yash Shah
2019-03-12 9:28 ` Borislav Petkov
2019-03-25 0:16 ` Paul Walmsley
2019-03-25 6:54 ` Borislav Petkov
2019-03-25 21:18 ` Paul Walmsley
2019-03-25 21:47 ` Borislav Petkov
2019-03-12 16:31 ` Paul Walmsley
2019-03-12 16:32 ` Paul Walmsley [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=alpine.DEB.2.21.9999.1903120925400.26459@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=palmer@sifive.com \
--cc=robh+dt@kernel.org \
--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).