public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: Sanjeev Premi <premi@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/3] Add support for OMAP35x processors
Date: Sun, 11 Jan 2009 00:16:18 +0200	[thread overview]
Message-ID: <20090110221618.GI25493@frodo> (raw)
In-Reply-To: <1231617637-18704-1-git-send-email-premi@ti.com>

On Sun, Jan 11, 2009 at 01:30:37AM +0530, Sanjeev Premi wrote:
> +config MACH_OMAP_LDP
> +	bool "OMAP3 LDP board"
> +	depends on ARCH_OMAP3 && ARCH_OMAP34XX && !ARCH_OMAP35XX
> +
>  config MACH_OMAP_3430SDP
>  	bool "OMAP 3430 SDP board"
> -	depends on ARCH_OMAP3 && ARCH_OMAP34XX
> +	depends on ARCH_OMAP3 && ARCH_OMAP34XX && !ARCH_OMAP35XX

This will prevent that we build a kernel for both 3430sdp and any
35xx-based board, right ?

>  
>  config MACH_OMAP3EVM
>  	bool "OMAP 3530 EVM board"
> -	depends on ARCH_OMAP3 && ARCH_OMAP34XX
> +	depends on ARCH_OMAP35XX

why removed ARCH_OMAP3 ??

-- 
balbi

  reply	other threads:[~2009-01-10 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10 20:00 [PATCH 1/3] Add support for OMAP35x processors Sanjeev Premi
2009-01-10 22:16 ` Felipe Balbi [this message]
2009-01-11 18:15   ` Premi, Sanjeev
  -- strict thread matches above, loose matches on Subject: below --
2008-09-01 19:57 Sanjeev Premi

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=20090110221618.GI25493@frodo \
    --to=me@felipebalbi.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox