From: Borislav Petkov <bp@alien8.de>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: michal.simek@xilinx.com, Shubhrajyoti.datta@xilinx.com,
mchehab@kernel.org, tony.luck@intel.com, james.morse@arm.com,
rric@kernel.org, linux-edac@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com
Subject: Re: [PATCH V2 2/2] EDAC: synopsys: re-enable the interrupts in intr_handler for V3.X Synopsys EDAC DDR
Date: Thu, 21 Apr 2022 11:06:54 +0200 [thread overview]
Message-ID: <YmEerhSXM0L8cUuj@zn.tnic> (raw)
In-Reply-To: <20220421015313.5747-3-sherry.sun@nxp.com>
On Thu, Apr 21, 2022 at 09:53:13AM +0800, Sherry Sun wrote:
> Since zynqmp_get_error_info() is called during CE/UE interrupt, at the
This also needs to be made human-readable: for example,
"zynqmp_get_error_info() reads the error information from the registers
when an interrupt for a {un-,}correctable error is raised."
> end of zynqmp_get_error_info(), it wirtes 0 to ECC_CLR_OFST, which cause
Unknown word [wirtes] in commit message.
Suggestions: ['writes',
Please introduce a spellchecker into your patch creation workflow.
> the CE/UE interrupts of V3.X Synopsys EDAC DDR been disabled, then the
"which disables the error interrupts" - make it simple - no need for the
V3.X marketing bla.
> interrupt handler will be called only once, so need to re-enable the
"Therefore, reenable the error interrupt line ..."
> interrupts at the end of intr_handler for V3.X Synopsys EDAC DDR.
I think you're catching my drift: our commit messages need to be
understandable and when read months, years from now, still to make
sense.
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> Reviewed-by: Shubhrajyoti Datta <Shubhrajyoti.datta@xilinx.com>
> Acked-by: Michal Simek <michal.simek@xilinx.com>
> ---
> Changes in V2:
> 1. Add the Reviewed-by and Acked-by tag.
> 2. Add the newline as suggested by Michal.
> ---
> drivers/edac/synopsys_edac.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/edac/synopsys_edac.c b/drivers/edac/synopsys_edac.c
> index 88a481043d4c..ae1cf02a92f5 100644
> --- a/drivers/edac/synopsys_edac.c
> +++ b/drivers/edac/synopsys_edac.c
> @@ -527,6 +527,8 @@ static void handle_error(struct mem_ctl_info *mci, struct synps_ecc_status *p)
> memset(p, 0, sizeof(*p));
> }
>
> +static void enable_intr(struct synps_edac_priv *priv);
Why the forward declaration?
Why not simply move {enable,disable}_intr() upwards in that file?
Also, for both fixes: do you want them backported in stable kernels?
I think you do because they look like you'd want that v3.x support to
work with older kernels too.
If so, read the section about "Fixes:" in
Documentation/process/submitting-patches.rst
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-21 9:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 1:53 [PATCH V2 0/2] EDAC: synopsys: fix some bugs in V3.X Synopsys EDAC DDR driver Sherry Sun
2022-04-21 1:53 ` [PATCH V2 1/2] EDAC: synopsys: Add disable_intr support for V3.X Synopsys EDAC DDR Sherry Sun
2022-04-21 8:58 ` Borislav Petkov
2022-04-21 1:53 ` [PATCH V2 2/2] EDAC: synopsys: re-enable the interrupts in intr_handler " Sherry Sun
2022-04-21 9:06 ` Borislav Petkov [this message]
2022-04-23 7:03 ` Sherry Sun
2022-04-26 14:58 ` Borislav Petkov
2022-04-27 1:40 ` Sherry Sun
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=YmEerhSXM0L8cUuj@zn.tnic \
--to=bp@alien8.de \
--cc=Shubhrajyoti.datta@xilinx.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michal.simek@xilinx.com \
--cc=rric@kernel.org \
--cc=sherry.sun@nxp.com \
--cc=tony.luck@intel.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