All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Borislav Petkov <bp@alien8.de>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: manual merge of the edac-amd tree with the edac tree
Date: Mon, 28 Nov 2016 14:37:26 +1100	[thread overview]
Message-ID: <20161128143726.7fda1849@canb.auug.org.au> (raw)

Hi Borislav,

Today's linux-next merge of the edac-amd tree got a conflict in:

  drivers/edac/edac_mc.c

between commit:

  ef91afa61088 ("edac: move documentation from edac_mc.c to edac_core.h")

from the edac tree and commit:

  c73e8833bec5 ("EDAC, mc: Fix locking around mc_devices list")

from the edac-amd tree.

I fixed it up (see below - there may be more fixes needed in
edac_core.h) and can carry the fix as necessary. This is now fixed as
far as linux-next is concerned, but any non trivial conflicts should be
mentioned to your upstream maintainer when your tree is submitted for
merging.  You may also want to consider cooperating with the maintainer
of the conflicting tree to minimise any particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/edac/edac_mc.c
index d50653d36918,d2ea9c4f1824..000000000000
--- a/drivers/edac/edac_mc.c
+++ b/drivers/edac/edac_mc.c
@@@ -470,6 -499,24 +470,17 @@@ static struct mem_ctl_info *__find_mci_
  
  	return NULL;
  }
+ 
 -/**
 - * find_mci_by_dev
 - *
 - *	scan list of controllers looking for the one that manages
 - *	the 'dev' device
 - * @dev: pointer to a struct device related with the MCI
 - */
+ struct mem_ctl_info *find_mci_by_dev(struct device *dev)
+ {
+ 	struct mem_ctl_info *ret;
+ 
+ 	mutex_lock(&mem_ctls_mutex);
+ 	ret = __find_mci_by_dev(dev);
+ 	mutex_unlock(&mem_ctls_mutex);
+ 
+ 	return ret;
+ }
  EXPORT_SYMBOL_GPL(find_mci_by_dev);
  
  /*
@@@ -599,10 -646,18 +610,12 @@@ static int del_mc_from_global_list(stru
  	return handlers;
  }
  
 -/**
 - * edac_mc_find: Search for a mem_ctl_info structure whose index is 'idx'.
 - *
 - * If found, return a pointer to the structure.
 - * Else return NULL.
 - */
  struct mem_ctl_info *edac_mc_find(int idx)
  {
+ 	struct mem_ctl_info *mci = NULL;
  	struct list_head *item;
- 	struct mem_ctl_info *mci;
+ 
+ 	mutex_lock(&mem_ctls_mutex);
  
  	list_for_each(item, &mc_devices) {
  		mci = list_entry(item, struct mem_ctl_info, link);

             reply	other threads:[~2016-11-28  3:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28  3:37 Stephen Rothwell [this message]
2016-11-28  8:27 ` linux-next: manual merge of the edac-amd tree with the edac tree 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

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=20161128143726.7fda1849@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mchehab@osg.samsung.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 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.