From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] update OMAP Kconfig help texts for all supported SoC models
Date: Wed, 22 Sep 2010 10:26:19 -0700 [thread overview]
Message-ID: <20100922172618.GD4211@atomide.com> (raw)
In-Reply-To: <20100922092752.GN27439@mail.wantstofly.org>
* Lennert Buytenhek <buytenh@wantstofly.org> [100922 02:19]:
> Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 553b7cf..15b603c 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -813,7 +813,7 @@ config ARCH_OMAP
> select GENERIC_CLOCKEVENTS
> select ARCH_HAS_HOLES_MEMORYMODEL
> help
> - Support for TI's OMAP platform (OMAP1 and OMAP2).
> + Support for TI's OMAP platform (OMAP1/2/3/4).
>
> config PLAT_SPEAR
> bool "ST SPEAr"
> diff --git a/arch/arm/plat-omap/Kconfig b/arch/arm/plat-omap/Kconfig
> index e39a417..68435c5 100644
> --- a/arch/arm/plat-omap/Kconfig
> +++ b/arch/arm/plat-omap/Kconfig
> @@ -19,7 +19,7 @@ config ARCH_OMAP2PLUS
> bool "TI OMAP2/3/4"
> select COMMON_CLKDEV
> help
> - "Systems based on omap24xx, omap34xx or omap44xx"
> + "Systems based on omap24xx, omap34xx, omap35xx or omap44xx"
>
> endchoice
It would be better to also use omap2/3/4 here too. Otherwise we
can easily miss some variants, like 36xx.
Tony
next prev parent reply other threads:[~2010-09-22 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 9:27 [PATCH] update OMAP Kconfig help texts for all supported SoC models Lennert Buytenhek
2010-09-22 17:26 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-22 18:40 Lennert Buytenhek
2010-09-22 20:10 ` 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=20100922172618.GD4211@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).