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 10:41:43 +0200 [thread overview]
Message-ID: <20150506084143.GA22949@pd.tnic> (raw)
In-Reply-To: <1430884947-16787-1-git-send-email-lho@apm.com>
On Tue, May 05, 2015 at 10:02:22PM -0600, Loc Ho wrote:
> This patch adds support for the APM X-Gene SoC memory controller EDAC driver
> for DT.
>
> v8:
> * Change ASM_EDAC_H to __ASM_EDAC_H in file edac.h
> * Add WARN_ONCE in stub function atomic_scrub
> * Update DTS binding documentation (with only memory controller node)
> * Temporary remove L1/L2, L3, and SoC driver code and update memory driver
> code accordingly
What does that mean exactly? They'll get added later?
It is called now xgene_edac_mc.c. Am I to expect more
xgene_edac_<functional_unit>.c submissions? What happened to building
everything around the shared IRQ handler?
Also, I see this SOB chain in some of the patches:
Signed-off-by: Feng Kan <fkan@apm.com>
Signed-off-by: Loc Ho <lho@apm.com>
and it is not clear who did what, from looking at the chain.
If you both authored the patches, you can write
Originally-by: Feng
[ Loc: did this and that]
Signed-off-by: Loc
for example.
See Documentation/SubmittingPatches for more info.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>
To: Loc Ho <lho-qTEPVZfXA3Y@public.gmane.org>
Cc: dougthompson-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org,
mchehab-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
linux-edac-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
jcm-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
patches-qTEPVZfXA3Y@public.gmane.org
Subject: Re: [PATCH v8 0/4] edac: Add APM X-Gene SoC memory controller EDAC driver
Date: Wed, 6 May 2015 10:41:43 +0200 [thread overview]
Message-ID: <20150506084143.GA22949@pd.tnic> (raw)
In-Reply-To: <1430884947-16787-1-git-send-email-lho-qTEPVZfXA3Y@public.gmane.org>
On Tue, May 05, 2015 at 10:02:22PM -0600, Loc Ho wrote:
> This patch adds support for the APM X-Gene SoC memory controller EDAC driver
> for DT.
>
> v8:
> * Change ASM_EDAC_H to __ASM_EDAC_H in file edac.h
> * Add WARN_ONCE in stub function atomic_scrub
> * Update DTS binding documentation (with only memory controller node)
> * Temporary remove L1/L2, L3, and SoC driver code and update memory driver
> code accordingly
What does that mean exactly? They'll get added later?
It is called now xgene_edac_mc.c. Am I to expect more
xgene_edac_<functional_unit>.c submissions? What happened to building
everything around the shared IRQ handler?
Also, I see this SOB chain in some of the patches:
Signed-off-by: Feng Kan <fkan-qTEPVZfXA3Y@public.gmane.org>
Signed-off-by: Loc Ho <lho-qTEPVZfXA3Y@public.gmane.org>
and it is not clear who did what, from looking at the chain.
If you both authored the patches, you can write
Originally-by: Feng
[ Loc: did this and that]
Signed-off-by: Loc
for example.
See Documentation/SubmittingPatches for more info.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-06 8:41 UTC|newest]
Thread overview: 33+ 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 ` Loc Ho
2015-05-06 4:02 ` [PATCH v8 1/5] arm64: Enable EDAC on ARM64 Loc Ho
2015-05-06 4:02 ` 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 ` 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 ` 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 ` 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:02 ` Loc Ho
2015-05-06 4:10 ` [PATCH v8 1/5] arm64: Enable EDAC on ARM64 Jon Masters
2015-05-06 4:10 ` Jon Masters
2015-05-06 8:41 ` Borislav Petkov [this message]
2015-05-06 8:41 ` [PATCH v8 0/4] edac: Add APM X-Gene SoC memory controller EDAC driver Borislav Petkov
2015-05-06 17:00 ` Loc Ho
2015-05-06 17:12 ` Borislav Petkov
2015-05-06 17:12 ` Borislav Petkov
2015-05-06 18:17 ` Loc Ho
2015-05-06 18:17 ` Loc Ho
2015-05-06 8:52 ` Arnd Bergmann
2015-05-06 8:52 ` Arnd Bergmann
2015-05-06 18:12 ` Loc Ho
2015-05-06 18:12 ` Loc Ho
2015-05-06 18:29 ` Borislav Petkov
2015-05-06 18:29 ` Borislav Petkov
2015-05-06 18:43 ` Loc Ho
2015-05-06 18:43 ` Loc Ho
2015-05-06 19:50 ` Arnd Bergmann
2015-05-06 19:50 ` Arnd Bergmann
2015-05-11 22:29 ` Loc Ho
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=20150506084143.GA22949@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.