linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Julien Grall <julien.grall@arm.com>,
	Christoffer Dall <christoffer.dall@linaro.org>
Subject: linux-next: manual merge of the clockevents tree with Linus' tree
Date: Tue, 7 Jun 2016 13:03:25 +1000	[thread overview]
Message-ID: <20160607130325.5d38931f@canb.auug.org.au> (raw)

Hi Daniel,

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

  drivers/clocksource/arm_arch_timer.c

between commit:

  d9b5e41591ca ("clocksource: arm_arch_timer: Extend arch_timer_kvm_info to get the virtual IRQ")

from Linus' tree and commit:

  e6f3cf51efde ("clocksource/drivers/arm_arch_timer: Convert init function to return error")

from the clockevents tree.

I fixed it up (see below) 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/clocksource/arm_arch_timer.c
index 4814446a0024,51042ed0d9ab..000000000000
--- a/drivers/clocksource/arm_arch_timer.c
+++ b/drivers/clocksource/arm_arch_timer.c
@@@ -743,13 -743,14 +744,18 @@@ static int __init arch_timer_init(void
  		}
  	}
  
- 	arch_timer_register();
- 	arch_timer_common_init();
+ 	ret = arch_timer_register();
+ 	if (ret)
+ 		return ret;
+ 
 -	return arch_timer_common_init();
++	ret = arch_timer_common_init();
 +
 +	arch_timer_kvm_info.virtual_irq = arch_timer_ppi[VIRT_PPI];
++
++	return ret;
  }
  
- static void __init arch_timer_of_init(struct device_node *np)
+ static int __init arch_timer_of_init(struct device_node *np)
  {
  	int i;
  

             reply	other threads:[~2016-06-07  3:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  3:03 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-11  5:24 linux-next: manual merge of the clockevents tree with Linus' tree Stephen Rothwell
2016-02-17  2:38 Stephen Rothwell
2013-12-20  4:09 Stephen Rothwell

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=20160607130325.5d38931f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=christoffer.dall@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=julien.grall@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).