From: Thomas Weber <thomas.weber.linux@googlemail.com>
To: felipe.balbi@nokia.com
Cc: ext Thomas Weber <weber@corscience.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH 2/9] OMAP: Devkit8000: Add missing package selection
Date: Wed, 24 Mar 2010 21:29:04 +0100 [thread overview]
Message-ID: <4BAA7610.2060004@gmail.com> (raw)
In-Reply-To: <20100324125817.GJ29419@nokia.com>
On 24.03.2010 13:58, Felipe Balbi wrote:
> On Wed, Mar 24, 2010 at 01:52:11PM +0100, ext Thomas Weber wrote:
>> Devkit8000 uses the CUS package for OMAP3530.
>>
>> This patch adds missing package selection for CUS and enables
>> CONFIG_MUX.
>>
>> Replace whitespace with tab in Kconfig.
>>
>> Signed-off-by: Thomas Weber <weber@corscience.de>
>> ---
>> arch/arm/mach-omap2/Kconfig | 6 ++++--
>> 1 files changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
>> index a8a3d1e..2455dcc 100644
>> --- a/arch/arm/mach-omap2/Kconfig
>> +++ b/arch/arm/mach-omap2/Kconfig
>> @@ -59,8 +59,10 @@ config MACH_OMAP3_BEAGLE
>> select OMAP_PACKAGE_CBB
>>
>> config MACH_DEVKIT8000
>> - bool "DEVKIT8000 board"
>> - depends on ARCH_OMAP3
>> + bool "DEVKIT8000 board"
>> + depends on ARCH_OMAP3
>> + select OMAP_PACKAGE_CUS
>> + select OMAP_MUX
>
> keep the formating, please.
>
Hello Felipe,
the mach_devkit8000 kconfig option is the only one of the board configs
that uses whitespaces for indention at the moment. Thatswhy I replaced
these whitespaces with one tab.
Thomas
next prev parent reply other threads:[~2010-03-24 20:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 12:52 [PATCH 0/9] OMAP: Devkit8000: Fix problems with package and usb Thomas Weber
2010-03-24 12:52 ` [PATCH 1/9] OMAP: Devkit8000: Fix typo in supplies Thomas Weber
2010-04-23 0:13 ` [APPLIED] " Tony Lindgren
2010-03-24 12:52 ` [PATCH 2/9] OMAP: Devkit8000: Add missing package selection Thomas Weber
2010-03-24 12:58 ` Felipe Balbi
2010-03-24 20:29 ` Thomas Weber [this message]
2010-03-25 7:42 ` Felipe Balbi
2010-04-23 0:14 ` [APPLIED] " Tony Lindgren
2010-03-24 12:52 ` [PATCH 3/9] OMAP: Devkit8000: Fix typo in pin name Thomas Weber
2010-04-23 0:14 ` [APPLIED] " Tony Lindgren
2010-03-24 12:52 ` [PATCH 4/9] OMAP: Devkit8000: Remove unnecessary include file Thomas Weber
2010-04-23 0:15 ` [APPLIED] " Tony Lindgren
2010-03-24 12:52 ` [PATCH 5/9] OMAP: Devkit8000: Change position of init calls Thomas Weber
2010-04-23 0:15 ` [APPLIED] " Tony Lindgren
2010-03-24 12:52 ` [PATCH 6/9] OMAP: Devkit8000: Remove unused pins Thomas Weber
2010-04-23 0:15 ` [APPLIED] " Tony Lindgren
2010-03-24 12:52 ` [PATCH 7/9] OMAP: Devkit8000: Fix wrong usb port on Devkit8000 Thomas Weber
2010-03-24 13:00 ` Felipe Balbi
2010-03-29 20:34 ` Felipe Balbi
2010-03-30 5:38 ` Gadiyar, Anand
2010-03-30 7:16 ` Thomas Weber
2010-03-30 6:29 ` Gadiyar, Anand
2010-04-07 17:47 ` Thomas Weber
2010-04-22 22:13 ` [APPLIED] " Tony Lindgren
2010-03-24 12:52 ` [PATCH 8/9] OMAP: Devkit8000: Add mux initialization Thomas Weber
2010-05-04 20:47 ` [APPLIED] " Tony Lindgren
2010-03-24 12:52 ` [PATCH 9/9] OMAP: Devkit8000: Update default configuration Thomas Weber
2010-05-04 20:49 ` [APPLIED] " Tony Lindgren
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=4BAA7610.2060004@gmail.com \
--to=thomas.weber.linux@googlemail.com \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=weber@corscience.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 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).