From: Manish Narani <MNARANI@xilinx.com>
To: Sherry Sun <sherry.sun@nxp.com>, "bp@alien8.de" <bp@alien8.de>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"rrichter@marvell.com" <rrichter@marvell.com>,
Michal Simek <michals@xilinx.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"frank.li@nxp.com" <frank.li@nxp.com>
Subject: RE: [PATCH v2] EDAC: synopsys: Fix the wrong call of pinf->col parameter
Date: Mon, 9 Mar 2020 08:44:44 +0000 [thread overview]
Message-ID: <DM6PR02MB44264FE7166FB2D23D4B4503C1FE0@DM6PR02MB4426.namprd02.prod.outlook.com> (raw)
In-Reply-To: <1582856183-5007-1-git-send-email-sherry.sun@nxp.com>
Hi,
> -----Original Message-----
> From: Sherry Sun <sherry.sun@nxp.com>
> Sent: Friday, February 28, 2020 7:46 AM
> To: bp@alien8.de; mchehab@kernel.org; tony.luck@intel.com;
> james.morse@arm.com; rrichter@marvell.com; Michal Simek
> <michals@xilinx.com>; Manish Narani <MNARANI@xilinx.com>
> Cc: linux-edac@vger.kernel.org; linux-kernel@vger.kernel.org; linux-
> imx@nxp.com; frank.li@nxp.com
> Subject: [PATCH v2] EDAC: synopsys: Fix the wrong call of pinf->col parameter
>
> Since ZynqMP platform call zynqmp_get_error_info() function to get ce/ue
> information. In this function, pinf->col parameter is not used, this
> parameter is only used by Zynq platforme in zynq_get_error_info(). So
> here pinf->col should not be called and printed for ZynqMP, need remove
> it.
>
> Fixes: b500b4a029d57 ("EDAC, synopsys: Add ECC support for ZynqMP DDR
> controller")
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
Reviewed-by: Manish Narani <manish.narani@xilinx.com>
Thanks,
Manish
next prev parent reply other threads:[~2020-03-09 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 2:16 Sherry Sun
2020-03-09 8:44 ` Manish Narani [this message]
2020-03-15 19:50 ` Borislav Petkov
2020-03-16 1:30 ` Sherry Sun
2020-03-16 10:43 ` Borislav Petkov
2020-03-16 12:28 ` 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=DM6PR02MB44264FE7166FB2D23D4B4503C1FE0@DM6PR02MB4426.namprd02.prod.outlook.com \
--to=mnarani@xilinx.com \
--cc=bp@alien8.de \
--cc=frank.li@nxp.com \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=michals@xilinx.com \
--cc=rrichter@marvell.com \
--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
all inboxes | Powered by JetHome®