backports.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: York Sun <york.sun@nxp.com>
To: Borislav Petkov <bp@alien8.de>, Tracy Smith <tlsmith3777@gmail.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"backports@vger.kernel.org" <backports@vger.kernel.org>,
	"linux-newbie@vger.kernel.org" <linux-newbie@vger.kernel.org>,
	"util-linux@vger.kernel.org" <util-linux@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: FW: edac driver initialization, interrupt, & debug
Date: Mon, 19 Nov 2018 15:55:44 +0000	[thread overview]
Message-ID: <AM0PR04MB3971E56F1DA8129F6DAAB7369AD80@AM0PR04MB3971.eurprd04.prod.outlook.com> (raw)
In-Reply-To: 20181117140513.GA4944@zn.tnic

On 11/17/18 6:05 AM, Borislav Petkov wrote:
> 
> Btw, looking at it, York, this whole injection functionality needs to
> be behind CONFIG_EDAC_DEBUG because a production driver shouldn't have
> injection capability.

I can make the change.

York
--
To unsubscribe from this list: send the line "unsubscribe backports" in

      parent reply	other threads:[~2018-11-19 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR02MB431115EC4735AE5B7E29F2CEF6DC0@BYAPR02MB4311.namprd02.prod.outlook.com>
     [not found] ` <BYAPR02MB43110062F32BFDEA712AB371F6DC0@BYAPR02MB4311.namprd02.prod.outlook.com>
     [not found]   ` <CAChUvXMp6S6MBY_LmrfgdPcctQw70FoyxbiHeFqK+5fQx5omCw@mail.gmail.com>
2018-11-16 17:07     ` FW: edac driver initialization, interrupt, & debug Tracy Smith
2018-11-17 14:05       ` Borislav Petkov
2018-11-17 23:22         ` Tracy Smith
2018-11-18  1:05           ` Steve Inkpen
2018-11-19 16:37             ` Tracy Smith
2018-11-19 16:48               ` York Sun
2018-11-21 17:01                 ` Tracy Smith
2018-11-21 22:02                   ` Tracy Smith
2018-11-19 16:24           ` FW: " York Sun
2018-11-19 15:55         ` York Sun [this message]

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=AM0PR04MB3971E56F1DA8129F6DAAB7369AD80@AM0PR04MB3971.eurprd04.prod.outlook.com \
    --to=york.sun@nxp.com \
    --cc=backports@vger.kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=tlsmith3777@gmail.com \
    --cc=util-linux@vger.kernel.org \
    /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).