From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver
Date: Thu, 30 Jul 2015 09:43:16 +0200 [thread overview]
Message-ID: <20150730074316.GB8984@nazgul.tnic> (raw)
In-Reply-To: <CAPw-ZTnipyRLnRxNTvq6FJTHyt2EbhObJMOa542LYOGna3FgjA@mail.gmail.com>
On Wed, Jul 29, 2015 at 10:31:49PM -0700, Loc Ho wrote:
> Let me clarify a bit. I have one top level driver node and multiple
> instance of subnodes - 4 MC, 4 L2/L1, 1 L3C, and 1 SoC EDAC for now.
> The L3C many be multiple instance in the future. Just a note, the way
> EDAC looks up instance is by pointer of struct device. It doesn't need
> anything more than that.
That's not what I mean - I mean all those instances calling into the
EDAC core concurrently without any locking. From a quick scan, nothing
problematic sticks out but it needs careful auditing.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-07-30 7:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 7:07 [PATCH v2 0/3] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver Loc Ho
2015-07-25 7:07 ` [PATCH v2 1/3] Documentation: Update the APM X-Gene SoC EDAC DTS binding for L3/SoC subnodes Loc Ho
2015-07-25 7:07 ` [PATCH v2 2/3] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver Loc Ho
2015-07-25 7:07 ` [PATCH v2 3/3] arm64: Add L3/SoC DT subnodes to the APM X-Gene SoC EDAC node Loc Ho
2015-07-29 14:29 ` [PATCH v2 2/3] edac: Add L3/SoC support to the APM X-Gene SoC EDAC driver Borislav Petkov
2015-07-29 23:39 ` Loc Ho
2015-07-30 4:31 ` Borislav Petkov
2015-07-30 5:31 ` Loc Ho
2015-07-30 7:43 ` Borislav Petkov [this message]
2015-08-10 16:37 ` [PATCH v2 0/3] " Dann Frazier
2015-08-10 20:15 ` Loc Ho
2015-08-11 14:36 ` Dann Frazier
2015-08-11 18:43 ` 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=20150730074316.GB8984@nazgul.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