All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Borislav Petkov <bp@suse.de>
Cc: Yazen Ghannam <Yazen.Ghannam@amd.com>, linux-next@vger.kernel.org
Subject: Re: [PATCH] EDAC: Document HW_EVENT_ERR_DEFERRED type
Date: Thu, 1 Dec 2016 20:00:15 -0200	[thread overview]
Message-ID: <20161201200015.616247fc@vento.lan> (raw)
In-Reply-To: <20161201214918.wjt2axxmuca65qip@pd.tnic>

Em Thu, 1 Dec 2016 22:49:18 +0100
Borislav Petkov <bp@suse.de> escreveu:

> On Thu, Dec 01, 2016 at 07:36:45PM -0200, Mauro Carvalho Chehab wrote:
> > I'm wandering if DEFERRED is the best name here... Maybe it could be
> > called, instead HW_EVENT_ERR_NON_URGENT or something like that.  
> 
> No, that's what the error is called in the hw documentation. It is
> really a *deferred* uncorrectable error. Deferred in the sense that it
> hasn't been consumed yet.

OK.

> > Boris, yeah, I can take care on it. I'll send my pull request
> > after yours, to avoid any issues.  
> 
> Ok, cool.
> 
> Thanks.

Patch applied.

Thanks!
Mauro

      reply	other threads:[~2016-12-01 22:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28  3:37 linux-next: manual merge of the edac-amd tree with the edac tree Stephen Rothwell
2016-11-28  8:27 ` Borislav Petkov
2016-11-30 10:50   ` Mauro Carvalho Chehab
2016-12-01 10:48     ` Borislav Petkov
2016-12-01 12:06       ` Mauro Carvalho Chehab
2016-12-01 16:02         ` Yazen Ghannam
2016-12-01 16:02           ` Yazen Ghannam
2016-12-01 18:15           ` Borislav Petkov
2016-12-01 19:57             ` Yazen Ghannam
2016-12-01 19:57               ` Yazen Ghannam
2016-12-01 20:24               ` [PATCH] EDAC: Document HW_EVENT_ERR_DEFERRED type Yazen Ghannam
2016-12-01 20:27                 ` Borislav Petkov
2016-12-01 21:36                   ` Mauro Carvalho Chehab
2016-12-01 21:49                     ` Borislav Petkov
2016-12-01 22:00                       ` Mauro Carvalho Chehab [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=20161201200015.616247fc@vento.lan \
    --to=mchehab@osg.samsung.com \
    --cc=Yazen.Ghannam@amd.com \
    --cc=bp@suse.de \
    --cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.