From: Nishanth Menon <menon.nishanth@gmail.com>
To: Khem Raj <kraj@mvista.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 5/11] Adding OMAP3430 support to mach-omap2
Date: Wed, 30 May 2007 20:01:09 -0500 [thread overview]
Message-ID: <465E1E55.2060001@gmail.com> (raw)
In-Reply-To: <200705301002.55697.kraj@mvista.com>
Khem Raj stated on 5/30/2007 12:02 PM:
> OMAP3430 being a omap3 family shouldn't this be be added in
> arch/arm/mach-omap3?
>
The files can either be reused from plat-omap or mach-omap2. 3430
closely follows 2420->2430 family line and adds more features and a new
ARM core (slightly unlike the jump in features from 1710->2420). IMHO,
does not make sense to call it mach-omap3..
Regards,
Nishanth Menon
next prev parent reply other threads:[~2007-05-31 1:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 6:21 [PATCH 5/11] Adding OMAP3430 support to mach-omap2 Syed Mohammed, Khasim
2007-05-29 16:49 ` Tony Lindgren
2007-05-29 17:33 ` Syed Mohammed, Khasim
2007-05-29 18:16 ` Tony Lindgren
2007-05-29 19:49 ` Syed Mohammed, Khasim
2007-05-29 20:23 ` Tony Lindgren
2007-05-30 17:02 ` Khem Raj
2007-05-31 1:01 ` Nishanth Menon [this message]
2007-05-31 3:29 ` Syed Mohammed, Khasim
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=465E1E55.2060001@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=kraj@mvista.com \
--cc=linux-omap-open-source@linux.omap.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