linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: omap2: Use a consistent AM33XX SoC option description
Date: Tue, 20 Aug 2013 13:42:53 -0300	[thread overview]
Message-ID: <20130820164251.GC4889@localhost> (raw)
In-Reply-To: <CABxcv=keV2Jf4gDwF477a9Msk6b-RgDBcxK1QyhchWffbKAoXw@mail.gmail.com>

On Fri, Aug 09, 2013 at 11:18:43AM +0200, Javier Martinez Canillas wrote:
> On Thu, Aug 8, 2013 at 11:32 PM, Ezequiel Garcia
> <ezequiel.garcia@free-electrons.com> wrote:
> > Fix the option description to match the other TI SoCs.
> > This is just a cosmetic change.
> >
> > Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> > ---
> >  arch/arm/mach-omap2/Kconfig | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
> > index 76170dd..56021c6 100644
> > --- a/arch/arm/mach-omap2/Kconfig
> > +++ b/arch/arm/mach-omap2/Kconfig
> > @@ -64,7 +64,7 @@ config SOC_OMAP5
> >         select ARM_ERRATA_798181 if SMP
> >
> >  config SOC_AM33XX
> > -       bool "AM33XX support"
> > +       bool "TI AM33XX"
> >         depends on ARCH_MULTI_V7
> >         select ARCH_OMAP2PLUS
> >         select ARM_CPU_SUSPEND if PM
> > --
> > 1.8.1.5
> >
> >
> 
> Reviewed-by: Javier Martinez Canillas <javier@dowhile0.org>

ping?
-- 
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2013-08-20 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 21:32 [PATCH] ARM: omap2: Use a consistent AM33XX SoC option description Ezequiel Garcia
2013-08-09  9:18 ` Javier Martinez Canillas
2013-08-20 16:42   ` Ezequiel Garcia [this message]
2013-08-21  7:55     ` 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=20130820164251.GC4889@localhost \
    --to=ezequiel.garcia@free-electrons.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).