All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alexander Shiyan <shc_work@mail.ru>
Subject: Re: linux-next: manual merge of the clockevents tree with the arm-soc tree
Date: Fri, 15 Jul 2016 19:06:57 +0200	[thread overview]
Message-ID: <57891831.2080806@linaro.org> (raw)
In-Reply-To: <20160711152812.3efd7047@canb.auug.org.au>

On 07/11/2016 07:28 AM, Stephen Rothwell wrote:
> Hi all,
> 
> On Thu, 7 Jul 2016 14:12:26 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Today's linux-next merge of the clockevents tree got a conflict in:
>>
>>   arch/arm/Kconfig
>>
>> between commit:
>>
>>   c86f51737f8d ("ARM: clps711x: Switch to MULTIPLATFORM")
>>
>> from the arm-soc tree and commit:
>>
>>   250e46aa3bb3 ("clocksource/drivers/clps_711x: Add the COMPILE_TEST option")
>>
>> from the clockevents tree.
>>
>> I fixed it up (I used the arm-soc version of this file and then added
>> the following merge fix patch) 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.
>>
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Thu, 7 Jul 2016 13:59:06 +1000
>> Subject: [PATCH] clocksource/drivers/clps_711x: fixup for "ARM: clps711x: Switch to MULTIPLATFORM"
>>
>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> ---
>>  arch/arm/mach-clps711x/Kconfig | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/mach-clps711x/Kconfig b/arch/arm/mach-clps711x/Kconfig
>> index 3b56197ccfd0..dc7c6edeab39 100644
>> --- a/arch/arm/mach-clps711x/Kconfig
>> +++ b/arch/arm/mach-clps711x/Kconfig
>> @@ -3,8 +3,8 @@ menuconfig ARCH_CLPS711X
>>  	depends on ARCH_MULTI_V4T
>>  	select ARCH_REQUIRE_GPIOLIB
>>  	select AUTO_ZRELADDR
>> -	select CLKSRC_MMIO
>>  	select CLKSRC_OF
>> +	select CLPS711X_TIMER
>>  	select COMMON_CLK
>>  	select CPU_ARM720T
>>  	select GENERIC_CLOCKEVENTS
>> -- 
>> 2.8.1
> 
> This merge fix is now applicable to the merge between the arm-soc tree
> and the tip tree.
> 
> Also, the clockevents tree needs to be cleaned up as all its commits
> have been added to the tip tree as different commits (but the s
> patches) :-(

I synced the branch with tip/timers/core, no more conflict should happen.

Thanks.

  -- Daniel


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

WARNING: multiple messages have this Message-ID (diff)
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the clockevents tree with the arm-soc tree
Date: Fri, 15 Jul 2016 19:06:57 +0200	[thread overview]
Message-ID: <57891831.2080806@linaro.org> (raw)
In-Reply-To: <20160711152812.3efd7047@canb.auug.org.au>

On 07/11/2016 07:28 AM, Stephen Rothwell wrote:
> Hi all,
> 
> On Thu, 7 Jul 2016 14:12:26 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> Today's linux-next merge of the clockevents tree got a conflict in:
>>
>>   arch/arm/Kconfig
>>
>> between commit:
>>
>>   c86f51737f8d ("ARM: clps711x: Switch to MULTIPLATFORM")
>>
>> from the arm-soc tree and commit:
>>
>>   250e46aa3bb3 ("clocksource/drivers/clps_711x: Add the COMPILE_TEST option")
>>
>> from the clockevents tree.
>>
>> I fixed it up (I used the arm-soc version of this file and then added
>> the following merge fix patch) 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.
>>
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Thu, 7 Jul 2016 13:59:06 +1000
>> Subject: [PATCH] clocksource/drivers/clps_711x: fixup for "ARM: clps711x: Switch to MULTIPLATFORM"
>>
>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> ---
>>  arch/arm/mach-clps711x/Kconfig | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/mach-clps711x/Kconfig b/arch/arm/mach-clps711x/Kconfig
>> index 3b56197ccfd0..dc7c6edeab39 100644
>> --- a/arch/arm/mach-clps711x/Kconfig
>> +++ b/arch/arm/mach-clps711x/Kconfig
>> @@ -3,8 +3,8 @@ menuconfig ARCH_CLPS711X
>>  	depends on ARCH_MULTI_V4T
>>  	select ARCH_REQUIRE_GPIOLIB
>>  	select AUTO_ZRELADDR
>> -	select CLKSRC_MMIO
>>  	select CLKSRC_OF
>> +	select CLPS711X_TIMER
>>  	select COMMON_CLK
>>  	select CPU_ARM720T
>>  	select GENERIC_CLOCKEVENTS
>> -- 
>> 2.8.1
> 
> This merge fix is now applicable to the merge between the arm-soc tree
> and the tip tree.
> 
> Also, the clockevents tree needs to be cleaned up as all its commits
> have been added to the tip tree as different commits (but the s
> patches) :-(

I synced the branch with tip/timers/core, no more conflict should happen.

Thanks.

  -- Daniel


-- 
 <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

  reply	other threads:[~2016-07-15 17:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  4:12 linux-next: manual merge of the clockevents tree with the arm-soc tree Stephen Rothwell
2016-07-07  4:12 ` Stephen Rothwell
2016-07-07  4:12 ` Stephen Rothwell
2016-07-11  5:28 ` Stephen Rothwell
2016-07-11  5:28   ` Stephen Rothwell
2016-07-11  5:28   ` Stephen Rothwell
2016-07-15 17:06   ` Daniel Lezcano [this message]
2016-07-15 17:06     ` Daniel Lezcano
2016-07-26 22:08 ` Stephen Rothwell
2016-07-26 22:08   ` Stephen Rothwell
2016-07-26 22:08   ` Stephen Rothwell
2016-08-01 23:24   ` Stephen Rothwell
2016-08-01 23:24     ` Stephen Rothwell
2016-08-01 23:24     ` Stephen Rothwell
2016-08-02  1:26     ` Linus Torvalds
2016-08-02  1:26       ` Linus Torvalds
2016-08-02  1:28       ` Linus Torvalds
2016-08-02  1:28         ` Linus Torvalds
2016-08-02  1:28         ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2017-04-10  3:18 Stephen Rothwell
2017-04-10  3:18 ` Stephen Rothwell
2016-06-07  2:56 Stephen Rothwell
2014-05-26  5:43 Stephen Rothwell
2014-05-26  5:43 ` Stephen Rothwell
2014-05-26  5:43 ` Stephen Rothwell
2014-05-26  6:03 ` Li.Xiubo
2014-05-26  6:03   ` Li.Xiubo at freescale.com
2014-05-26  7:49 ` Shawn Guo
2014-05-26  7:49   ` Shawn Guo
2014-05-26  7:49   ` Shawn Guo

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=57891831.2080806@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=arnd@arndb.de \
    --cc=hpa@zytor.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=olof@lixom.net \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=shc_work@mail.ru \
    --cc=tglx@linutronix.de \
    /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.