From: Shubhrajyoti Datta <shubhraj@xilinx.com>
To: Michal Simek <michals@xilinx.com>,
Sherry Sun <sherry.sun@nxp.com>, "bp@alien8.de" <bp@alien8.de>,
"mchehab@kernel.org" <mchehab@kernel.org>,
Michal Simek <michals@xilinx.com>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"rric@kernel.org" <rric@kernel.org>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-imx@nxp.com" <linux-imx@nxp.com>
Subject: RE: [PATCH 0/2] fix some bugs in V3.X Synopsys EDAC DDR driver
Date: Tue, 19 Apr 2022 15:34:15 +0000 [thread overview]
Message-ID: <DM6PR02MB6635A97A9D7AC2A061188F84AAF29@DM6PR02MB6635.namprd02.prod.outlook.com> (raw)
In-Reply-To: <ea5cc404-ab52-0df0-d3a7-f010e708a12d@xilinx.com>
> -----Original Message-----
> From: Michal Simek <michal.simek@xilinx.com>
> Sent: Friday, March 18, 2022 5:00 PM
> To: Sherry Sun <sherry.sun@nxp.com>; bp@alien8.de;
> mchehab@kernel.org; Michal Simek <michals@xilinx.com>;
> tony.luck@intel.com; james.morse@arm.com; rric@kernel.org;
> Shubhrajyoti Datta <shubhraj@xilinx.com>
> Cc: linux-edac@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; linux-imx@nxp.com
> Subject: Re: [PATCH 0/2] fix some bugs in V3.X Synopsys EDAC DDR driver
>
> +Shubhrajyoti.
>
> On 3/18/22 12:17, Sherry Sun wrote:
> > The two patches fix some issues for V3.X Synopsys EDAC DDR in
> synopsys_edac.c.
> > For the details, please check the patch commit log. This has been
> > verified on i.MX8MP platform.
> >
The changes look good to me .
Reviewed-by: Shubhrajyoti Datta <Shubhrajyoti.datta@xilinx.com>
> > Sherry Sun (2):
> > EDAC: synopsys: Add disable_intr support for V3.X Synopsys EDAC DDR
> > EDAC: synopsys: re-enable the interrupts in intr_handler for V3.X
> > Synopsys EDAC DDR
> >
> > drivers/edac/synopsys_edac.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
_______________________________________________
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-19 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 11:17 [PATCH 0/2] fix some bugs in V3.X Synopsys EDAC DDR driver Sherry Sun
2022-03-18 11:17 ` [PATCH 1/2] EDAC: synopsys: Add disable_intr support for V3.X Synopsys EDAC DDR Sherry Sun
2022-04-20 5:56 ` Michal Simek
2022-03-18 11:17 ` [PATCH 2/2] EDAC: synopsys: re-enable the interrupts in intr_handler " Sherry Sun
2022-04-20 5:57 ` Michal Simek
2022-04-20 6:23 ` Sherry Sun
2022-03-18 11:30 ` [PATCH 0/2] fix some bugs in V3.X Synopsys EDAC DDR driver Michal Simek
2022-04-19 15:34 ` Shubhrajyoti Datta [this message]
2022-03-25 1:28 ` Sherry Sun
2022-04-18 2:27 ` Sherry Sun
2022-04-18 8:34 ` Borislav Petkov
2022-04-18 10:12 ` Sherry Sun
2022-04-18 10:20 ` Borislav Petkov
2022-04-18 10:26 ` 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=DM6PR02MB6635A97A9D7AC2A061188F84AAF29@DM6PR02MB6635.namprd02.prod.outlook.com \
--to=shubhraj@xilinx.com \
--cc=bp@alien8.de \
--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=michals@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;
as well as URLs for NNTP newsgroup(s).