All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Hemant Pedanekar <hemantp@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND v5 0/3] Add support for TI814X processor series
Date: Mon, 12 Dec 2011 10:25:16 -0800	[thread overview]
Message-ID: <20111212182515.GG31337@atomide.com> (raw)
In-Reply-To: <1323482305-32155-1-git-send-email-hemantp@ti.com>

* Hemant Pedanekar <hemantp@ti.com> [111209 17:27]:
> This patch set adds support for DM814x/AM387x device series having Cortex-A8
> MPU.
> 
> The technical documents are available from following link:
> 
> http://focus.ti.com/docs/prod/folders/print/tms320dm8148.html
> 
> This series is referred in code as TI814X.
> 
> Since these devices share similar architecture as TI816X devices, existing
> TI816X code is updated to accomodate TI814X support. The code shared across
> TI816X and TI814X devices is updated with TI81XX/ti81xx prefix as applicable,
> while maintaining cpu_is_ti816x() and cpu_is_ti814x() to distinguish specific
> execution differences.

Thanks applying 1 & 2 into soc branch and 3 into board branch.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v5 0/3] Add support for TI814X processor series
Date: Mon, 12 Dec 2011 10:25:16 -0800	[thread overview]
Message-ID: <20111212182515.GG31337@atomide.com> (raw)
In-Reply-To: <1323482305-32155-1-git-send-email-hemantp@ti.com>

* Hemant Pedanekar <hemantp@ti.com> [111209 17:27]:
> This patch set adds support for DM814x/AM387x device series having Cortex-A8
> MPU.
> 
> The technical documents are available from following link:
> 
> http://focus.ti.com/docs/prod/folders/print/tms320dm8148.html
> 
> This series is referred in code as TI814X.
> 
> Since these devices share similar architecture as TI816X devices, existing
> TI816X code is updated to accomodate TI814X support. The code shared across
> TI816X and TI814X devices is updated with TI81XX/ti81xx prefix as applicable,
> while maintaining cpu_is_ti816x() and cpu_is_ti814x() to distinguish specific
> execution differences.

Thanks applying 1 & 2 into soc branch and 3 into board branch.

Regards,

Tony

  parent reply	other threads:[~2011-12-12 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10  1:58 [PATCH RESEND v5 0/3] Add support for TI814X processor series Hemant Pedanekar
2011-12-10  1:58 ` Hemant Pedanekar
2011-12-10  1:58 ` [PATCH RESEND v5 1/3] ARM: OMAP: TI81XX: Prepare for addition of TI814X support Hemant Pedanekar
2011-12-10  1:58   ` Hemant Pedanekar
2011-12-10  1:58 ` [PATCH RESEND v5 2/3] ARM: OMAP: TI814X: Add cpu type macros and detection support Hemant Pedanekar
2011-12-10  1:58   ` Hemant Pedanekar
2011-12-10  1:58 ` [PATCH RESEND v5 3/3] ARM: OMAP: TI814X: Create board support and enable build for TI8148 EVM Hemant Pedanekar
2011-12-10  1:58   ` Hemant Pedanekar
2011-12-12 18:25 ` Tony Lindgren [this message]
2011-12-12 18:25   ` [PATCH RESEND v5 0/3] Add support for TI814X processor series Tony Lindgren
  -- strict thread matches above, loose matches on Subject: below --
2011-12-10  1:44 Hemant Pedanekar
2011-12-10  1:44 ` Hemant Pedanekar

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=20111212182515.GG31337@atomide.com \
    --to=tony@atomide.com \
    --cc=hemantp@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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 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.