All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Pedanekar, Hemant" <hemantp@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Hilman, Kevin" <khilman@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH v4 1/3] ARM: OMAP: TI81XX: Prepare for addition of TI814X support
Date: Fri, 9 Dec 2011 12:52:04 -0800	[thread overview]
Message-ID: <20111209205203.GV31337@atomide.com> (raw)
In-Reply-To: <DDE393F022194E4FB9AE108B0AECD70C042A54@DBDE01.ent.ti.com>

* Pedanekar, Hemant <hemantp@ti.com> [111209 09:57]:
> Tony Lindgren wrote on Thursday, December 08, 2011 4:48 AM:
> 
> > * Hemant Pedanekar <hemantp@ti.com> [111009 18:06]:
> >> This patch updates existing macros, functions used for TI816X, to enable
> >> addition of other SoCs belonging to TI81XX family (e.g., TI814X).
> >> 
> >> The approach taken is to use TI81XX/ti81xx for code/data going to be
> >> common across all TI81XX devices. 
> >> 
> >> cpu_is_ti81xx() is introduced to handle code common across TI81XX devices.
> >> 
> >> In addition, ti8168_evm_map_io() is now replaced with ti81xx_map_io() and
> >> moved in mach-omap2/common.c as same will be used for TI814X and is not
> >> board specific.
> > 
> > Looks like this series needs a rebase after the map_io and common.h
> > changes. Can you please rebase against the current omap soc branch at
> > commit 24a5e092a387e4c8e93f33448da334bd3fd15192?
> > 
> > Regards,
> > 
> > Tony
> 
> Thanks Tony, I sent v5 in the morning but it didnlt reach the ML
> may be because I got unsubscribed for some reason.

Yeah not seeing it :(
 
> Btw, I am getting following error when trying to build from soc branch:
> 
> make[1]: *** No rule to make target `arch/arm/mach-omap2/omap-smc.o', needed by `arch/arm/mach-omap2/built-in.o'.  Stop.
> 
> Looks like the commit c95f06a0d4bc9c2546769b5d984cc2dc6665d4f5 added
> Following but not the corresponding c file(s):
> 
>  +secure-common                          = omap-smc.o omap-secure.o

Thanks for letting me know, that means there's a dependency to the omap4
branch, I'll update the soc branch accordingly.

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 v4 1/3] ARM: OMAP: TI81XX: Prepare for addition of TI814X support
Date: Fri, 9 Dec 2011 12:52:04 -0800	[thread overview]
Message-ID: <20111209205203.GV31337@atomide.com> (raw)
In-Reply-To: <DDE393F022194E4FB9AE108B0AECD70C042A54@DBDE01.ent.ti.com>

* Pedanekar, Hemant <hemantp@ti.com> [111209 09:57]:
> Tony Lindgren wrote on Thursday, December 08, 2011 4:48 AM:
> 
> > * Hemant Pedanekar <hemantp@ti.com> [111009 18:06]:
> >> This patch updates existing macros, functions used for TI816X, to enable
> >> addition of other SoCs belonging to TI81XX family (e.g., TI814X).
> >> 
> >> The approach taken is to use TI81XX/ti81xx for code/data going to be
> >> common across all TI81XX devices. 
> >> 
> >> cpu_is_ti81xx() is introduced to handle code common across TI81XX devices.
> >> 
> >> In addition, ti8168_evm_map_io() is now replaced with ti81xx_map_io() and
> >> moved in mach-omap2/common.c as same will be used for TI814X and is not
> >> board specific.
> > 
> > Looks like this series needs a rebase after the map_io and common.h
> > changes. Can you please rebase against the current omap soc branch at
> > commit 24a5e092a387e4c8e93f33448da334bd3fd15192?
> > 
> > Regards,
> > 
> > Tony
> 
> Thanks Tony, I sent v5 in the morning but it didnlt reach the ML
> may be because I got unsubscribed for some reason.

Yeah not seeing it :(
 
> Btw, I am getting following error when trying to build from soc branch:
> 
> make[1]: *** No rule to make target `arch/arm/mach-omap2/omap-smc.o', needed by `arch/arm/mach-omap2/built-in.o'.  Stop.
> 
> Looks like the commit c95f06a0d4bc9c2546769b5d984cc2dc6665d4f5 added
> Following but not the corresponding c file(s):
> 
>  +secure-common                          = omap-smc.o omap-secure.o

Thanks for letting me know, that means there's a dependency to the omap4
branch, I'll update the soc branch accordingly.

Regards,

Tony

  reply	other threads:[~2011-12-09 20:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10  1:39 [PATCH v4 1/3] ARM: OMAP: TI81XX: Prepare for addition of TI814X support Hemant Pedanekar
2011-10-10  1:39 ` Hemant Pedanekar
2011-12-07 23:17 ` Tony Lindgren
2011-12-07 23:17   ` Tony Lindgren
2011-12-09 18:29   ` Pedanekar, Hemant
2011-12-09 18:29     ` Pedanekar, Hemant
2011-12-09 20:52     ` Tony Lindgren [this message]
2011-12-09 20:52       ` 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=20111209205203.GV31337@atomide.com \
    --to=tony@atomide.com \
    --cc=hemantp@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    /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.