All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Borislav Petkov <bp@alien8.de>, Yazen Ghannam <Yazen.Ghannam@amd.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the edac-amd tree with the edac tree
Date: Thu, 1 Dec 2016 10:06:17 -0200	[thread overview]
Message-ID: <20161201100617.511d8aae@vento.lan> (raw)
In-Reply-To: <20161201104846.kjvuy5tj475oxzke@pd.tnic>

Em Thu, 1 Dec 2016 11:48:46 +0100
Borislav Petkov <bp@alien8.de> escreveu:

> On Wed, Nov 30, 2016 at 08:50:13AM -0200, Mauro Carvalho Chehab wrote:
> > Fixed. If you have a stable branch, I can rebase it on the top
> > of your patches, in order to avoid the confict at linux-next.
> 
> http://git.kernel.org/cgit/linux/kernel/git/bp/bp.git/log/?h=for-next

Thanks!

> but with that fixed, shouldn't the merge work without a conflict?

Well, we're removing some lines from one file and adding them on another
one. Git is not smart enough to solve such conflicts automatically:

	CONFLICT (content): Merge conflict in drivers/edac/edac_mc.c
	Recorded preimage for 'drivers/edac/edac_mc.c'
	Automatic merge failed; fix conflicts and then commit the result.

Anyway, I rebased my work on the top of your branch. The conflict
is now gone:

	https://git.kernel.org/cgit/linux/kernel/git/mchehab/linux-edac.git/log/?h=linux_next

You can see the generated documentation at:
	https://mchehab.fedorapeople.org/kernel_docs/admin-guide/ras.html
	(user and admin guide)
and:
	https://mchehab.fedorapeople.org/kernel_docs/driver-api/edac.html
	(kernel API)

However, rebasing over your tree showed a new documentation gap:
	./include/linux/edac.h:144: warning: Enum value 'HW_EVENT_ERR_DEFERRED' not described in enum 'hw_event_mc_err_type'

With was introduced by this commit:

  commit d12a969ebbfcfc25853c4147d42b388f758e8784
  Author: Yazen Ghannam <Yazen.Ghannam@amd.com>
  Date:   Thu Nov 17 17:57:32 2016 -0500

    EDAC, amd64: Add Deferred Error type
    
    Currently, deferred errors are classified as correctable in EDAC. Add a
    new error type for deferred errors so that they are correctly reported
    to the user.
    
    Signed-off-by: Yazen Ghannam <Yazen.Ghannam@amd.com>
    Cc: Aravind Gopalakrishnan <aravindksg.lkml@gmail.com>
    Cc: linux-edac <linux-edac@vger.kernel.org>
    Link: http://lkml.kernel.org/r/1479423463-8536-7-git-send-email-Yazen.Ghannam@amd.com
    Signed-off-by: Borislav Petkov <bp@suse.de>


Yazen introduced a "deferred error" code (whatever it means), but didn't
document what's that. Unfortunately, the patch description is also
not clear enough about what a "deferred error" means or how userspace
is supposed to handle it.

Yazen,

Could you please send us a patch adding a proper description for this
new error code?

Thanks!
Mauro

  reply	other threads:[~2016-12-01 12:06 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 [this message]
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

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=20161201100617.511d8aae@vento.lan \
    --to=mchehab@osg.samsung.com \
    --cc=Yazen.Ghannam@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.