From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/4] edac: Add APM X-Gene SoC memory controller EDAC driver
Date: Wed, 6 May 2015 19:12:42 +0200 [thread overview]
Message-ID: <20150506171242.GG22949@pd.tnic> (raw)
In-Reply-To: <CAPw-ZT=LepJr2Smjy81yhcTANdMRw99x1vR9rMoYsnHW_P3HPg@mail.gmail.com>
On Wed, May 06, 2015 at 10:00:45AM -0700, Loc Ho wrote:
> It was discussed with Rob already in previous email. As we don't touch
> the shared status registers besides reading status, it will just
> register as shared interrupt.
I don't see why that justifies the addition of an
edac_xgene-<functional_unit> compilation unit and thus an .ko module per
shared interrupt handler.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-05-06 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 4:02 [PATCH v8 0/4] edac: Add APM X-Gene SoC memory controller EDAC driver Loc Ho
2015-05-06 4:02 ` [PATCH v8 1/5] arm64: Enable EDAC on ARM64 Loc Ho
2015-05-06 4:02 ` [PATCH v8 2/5] MAINTAINERS: Add entry for APM X-Gene SoC EDAC driver Loc Ho
2015-05-06 4:02 ` [PATCH v8 3/5] Documentation: Add documentation for the APM X-Gene SoC EDAC DTS binding Loc Ho
2015-05-06 4:02 ` [PATCH v8 4/5] edac: Add APM X-Gene SoC memory controller EDAC driver Loc Ho
2015-05-06 4:02 ` [PATCH v8 5/5] arm64: Add APM X-Gene SoC memory controller EDAC DTS entries Loc Ho
2015-05-06 4:10 ` [PATCH v8 1/5] arm64: Enable EDAC on ARM64 Jon Masters
2015-05-06 8:41 ` [PATCH v8 0/4] edac: Add APM X-Gene SoC memory controller EDAC driver Borislav Petkov
[not found] ` <CAPw-ZT=LepJr2Smjy81yhcTANdMRw99x1vR9rMoYsnHW_P3HPg@mail.gmail.com>
2015-05-06 17:12 ` Borislav Petkov [this message]
2015-05-06 18:17 ` Loc Ho
2015-05-06 8:52 ` Arnd Bergmann
2015-05-06 18:12 ` Loc Ho
2015-05-06 18:29 ` Borislav Petkov
2015-05-06 18:43 ` Loc Ho
2015-05-06 19:50 ` Arnd Bergmann
2015-05-11 22:29 ` Loc Ho
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=20150506171242.GG22949@pd.tnic \
--to=bp@alien8.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).