From: Borislav Petkov <bp@alien8.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Medad Young <medadyoung@gmail.com>,
rric@kernel.org, James Morse <james.morse@arm.com>,
tony.luck@intel.com, Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Benjamin Fair <benjaminfair@google.com>,
Nancy Yuen <yuenn@google.com>,
Patrick Venture <venture@google.com>,
KWLIU@nuvoton.com, YSCHU@nuvoton.com, JJLIU0@nuvoton.com,
KFTING <KFTING@nuvoton.com>, Avi Fishman <avifishman70@gmail.com>,
Tomer Maimon <tmaimon77@gmail.com>,
Tali Perry <tali.perry1@gmail.com>,
ctcchien@nuvoton.com, devicetree <devicetree@vger.kernel.org>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-edac <linux-edac@vger.kernel.org>
Subject: Re: [PATCH v6 3/3] EDAC: nuvoton: Add NPCM memory controller driver
Date: Thu, 14 Apr 2022 12:15:37 +0200 [thread overview]
Message-ID: <Ylf0Sc7fqv25Ay05@zn.tnic> (raw)
In-Reply-To: <14d07709-07ef-21a8-ad74-0f56447cf6dd@molgen.mpg.de>
On Thu, Apr 14, 2022 at 10:56:43AM +0200, Paul Menzel wrote:
> No idea, why you had to ask this question, while you statement before
> already made the point.
You've told Medad one thing. I told him the complete opposite. Medad as
new submitter gets confused. And I don't want patch submitters to get
confused by review.
So, if you're unsure about a review feedback, don't give it pls.
> Sorry I do not get your point. Would you elaborate on the debug message so
> it’s more useful?
Just think of the big picture: is my error message useful enough for
debugging or would I have to go and add more info to it so that I can
debug an issue?
Example:
There is
edac_dbg(3, "InterruptStatus : 0x%x\n", intr_status);
now.
Now, how about this?
edac_dbg(3, "dev: %s, id: %s: IRQ: %d, interrupt status: 0x%x\n",
mci->dev_name, mci->ctl_name, irq, intr_status);
Which one, do you think, is more helpful to a person trying to debug any
potential issue with the interrupt handler and the ECCs it is supposed
to issue?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-04-14 10:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 3:01 [PATCH v6 0/3] EDAC: nuvoton: Add nuvoton NPCM memory controller driver Medad CChien
2022-03-22 3:01 ` [PATCH v6 1/3] ARM: dts: nuvoton: Add memory controller node Medad CChien
2022-04-08 17:02 ` Borislav Petkov
2022-04-09 5:57 ` Paul Menzel
2022-04-11 7:56 ` Medad Young
2022-04-11 8:12 ` Paul Menzel
2022-03-22 3:01 ` [PATCH v6 2/3] dt-bindings: edac: nuvoton: add NPCM memory controller Medad CChien
2022-03-23 15:56 ` Rob Herring
2022-04-08 17:05 ` Borislav Petkov
2022-04-11 7:57 ` Medad Young
2022-04-11 8:21 ` Borislav Petkov
2022-04-09 6:12 ` Paul Menzel
2022-04-11 8:01 ` Medad Young
2022-03-22 3:01 ` [PATCH v6 3/3] EDAC: nuvoton: Add NPCM memory controller driver Medad CChien
2022-04-08 19:04 ` Borislav Petkov
2022-04-11 8:06 ` Medad Young
2022-04-09 7:08 ` Paul Menzel
2022-04-14 1:55 ` Medad Young
2022-04-14 8:42 ` Borislav Petkov
2022-04-14 8:56 ` Paul Menzel
2022-04-14 10:15 ` Borislav Petkov [this message]
2022-04-14 10:44 ` Paul Menzel
2022-04-14 11:38 ` 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=Ylf0Sc7fqv25Ay05@zn.tnic \
--to=bp@alien8.de \
--cc=JJLIU0@nuvoton.com \
--cc=KFTING@nuvoton.com \
--cc=KWLIU@nuvoton.com \
--cc=YSCHU@nuvoton.com \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=ctcchien@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=medadyoung@gmail.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
--cc=robh+dt@kernel.org \
--cc=rric@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=tony.luck@intel.com \
--cc=venture@google.com \
--cc=yuenn@google.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).