From: Borislav Petkov <bp@alien8.de>
To: Yash Shah <yash.shah@sifive.com>, James Morse <james.morse@arm.com>
Cc: aou@eecs.berkeley.edu, paulmck@linux.ibm.com,
gregkh@linuxfoundation.org, Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, nicolas.ferre@microchip.com,
Sachin Ghadi <sachin.ghadi@sifive.com>,
James Morse <james.morse@arm.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org, mchehab@kernel.org,
davem@davemloft.net, linux-edac@vger.kernel.org
Subject: Re: [PATCH v2] edac: sifive: Add EDAC platform driver for SiFive SoCs
Date: Tue, 21 May 2019 20:21:32 +0200 [thread overview]
Message-ID: <20190521182132.GB7793@cz.tnic> (raw)
In-Reply-To: <CAJ2_jOG9Ag0spbh3YCxavUE5XEAUP1pHcgCZ56Nu2u4TqfrzHQ@mail.gmail.com>
On Tue, May 21, 2019 at 11:00:59AM +0530, Yash Shah wrote:
> The prerequisite patch (sifive_l2_cache driver) has been merged into
> mainline v5.2-rc1
> It should be OK to merge this edac driver now.
James?
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply. Srsly.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-05-21 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 11:27 [PATCH v2] EDAC support for SiFive SoCs Yash Shah
2019-05-06 11:27 ` [PATCH v2] edac: sifive: Add EDAC platform driver " Yash Shah
2019-05-21 5:30 ` Yash Shah
2019-05-21 18:21 ` Borislav Petkov [this message]
2019-05-22 9:13 ` James Morse
2019-05-22 9:34 ` Boris Petkov
2019-06-07 6:43 ` Borislav Petkov
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=20190521182132.GB7793@cz.tnic \
--to=bp@alien8.de \
--cc=aou@eecs.berkeley.edu \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@linux.ibm.com \
--cc=sachin.ghadi@sifive.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).