public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Russell King <rmk@arm•linux.org.uk>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Dave Martin <dave.martin@linaro•org>
Subject: linux-next: manual merge of the arm tree with the arm-current tree
Date: Wed, 15 Dec 2010 10:54:35 +1100	[thread overview]
Message-ID: <20101215105435.3ce83f21.sfr@canb.auug.org.au> (raw)

Hi Russell,

Today's linux-next merge of the arm tree got a conflict in
arch/arm/Kconfig between commit 6e6fc998b8c127fe06b9350a1f16e41bfe4f109d
("ARM: 6533/1: Thumb-2: Make CONFIG_THUMB2_KERNEL depend on !CPU_V6")
from the arm-current tree and commit
4a50bfe365a977f634311504484342fbfffe855c ("ARM: Ensure experimental
options are so marked") from the arm tree.

Just context changes.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc arch/arm/Kconfig
index d56d21c0,e77fe0f..0000000
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@@ -1310,8 -1319,8 +1319,8 @@@ config H
  	default 100
  
  config THUMB2_KERNEL
- 	bool "Compile the kernel in Thumb-2 mode"
+ 	bool "Compile the kernel in Thumb-2 mode (EXPERIMENTAL)"
 -	depends on CPU_V7 && EXPERIMENTAL
 +	depends on CPU_V7 && !CPU_V6 && EXPERIMENTAL
  	select AEABI
  	select ARM_ASM_UNIFIED
  	help

             reply	other threads:[~2010-12-14 23:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 23:54 Stephen Rothwell [this message]
2010-12-14 23:57 ` linux-next: manual merge of the arm tree with the arm-current tree Russell King
2010-12-15 12:28   ` Dave Martin
2010-12-15 16:43     ` Russell King
  -- strict thread matches above, loose matches on Subject: below --
2010-12-05 23:58 Stephen Rothwell
2010-10-11 23:33 Stephen Rothwell
2010-10-12  8:03 ` Uwe Kleine-König
2010-10-12  8:28   ` Russell King
2010-10-12  9:23     ` Uwe Kleine-König
2010-10-12  9:42       ` Russell King
2010-10-12 10:02         ` Uwe Kleine-König
2010-10-12 10:35 ` Sascha Hauer
2010-10-11  1:24 Stephen Rothwell
2010-10-11  7:48 ` Anders Larsen
2010-09-27  4:21 Stephen Rothwell
2010-07-26  1:13 Stephen Rothwell
2010-02-02  0:07 Stephen Rothwell
2010-01-17 23:35 Stephen Rothwell
2010-01-18  1:33 ` Ben Dooks
2010-01-18  3:34   ` Stephen Rothwell
2009-05-06  1:32 Stephen Rothwell
2009-03-23  0:06 Stephen Rothwell
2009-02-15 23:39 Stephen Rothwell
2009-02-16  0:18 ` Ryan Mallon
2009-02-16  0:29   ` Russell King

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=20101215105435.3ce83f21.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=dave.martin@linaro$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rmk@arm$(echo .)linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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