From: Sherry Sun <sherry.sun@nxp.com>
To: Borislav Petkov <bp@alien8.de>,
"michal.simek@xilinx.com" <michal.simek@xilinx.com>
Cc: "mchehab@kernel.org" <mchehab@kernel.org>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"rric@kernel.org" <rric@kernel.org>,
"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>,
dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH 0/2] fix some bugs in V3.X Synopsys EDAC DDR driver
Date: Mon, 18 Apr 2022 10:12:14 +0000 [thread overview]
Message-ID: <AS8PR04MB840435F6BACFF0C7F9B6D90792F39@AS8PR04MB8404.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <Yl0iqXnsFm8rMBms@zn.tnic>
Hi Borislav, thanks for the info. Hi Michal, would you please help review the patch set? Thanks a lot!
Best regards
Sherry
> -----Original Message-----
> From: Borislav Petkov <bp@alien8.de>
> Sent: 2022年4月18日 16:35
> To: Sherry Sun <sherry.sun@nxp.com>; michal.simek@xilinx.com
> Cc: 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; dl-linux-imx <linux-imx@nxp.com>
> Subject: Re: [PATCH 0/2] fix some bugs in V3.X Synopsys EDAC DDR driver
>
> On Mon, Apr 18, 2022 at 02:27:21AM +0000, Sherry Sun wrote:
> > Hi Borislav, do you have any comments regarding this patch set?
>
> Yes, for EDAC drivers which have designated maintainers, I usually wait first
> for them to have a look. In this case, Michal.
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpeopl
> e.kernel.org%2Ftglx%2Fnotes-about-
> netiquette&data=04%7C01%7Csherry.sun%40nxp.com%7Ccea2785e929
> f44e59a4b08da211652b6%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C
> 0%7C637858677007128155%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wL
> jAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&
> ;sdata=d7zJS1kgETYnQXkBO4K3m1D5cvFlJ75BID%2B8Fjy8a0A%3D&rese
> rved=0
_______________________________________________
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-18 10:28 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
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 [this message]
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=AS8PR04MB840435F6BACFF0C7F9B6D90792F39@AS8PR04MB8404.eurprd04.prod.outlook.com \
--to=sherry.sun@nxp.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=michal.simek@xilinx.com \
--cc=rric@kernel.org \
--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).