From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [Patch 1/3] U-Boot-V2:Board:OMAP common board.h
Date: Tue, 22 Jul 2008 06:32:17 -0500 [thread overview]
Message-ID: <4885C541.9090604@gmail.com> (raw)
In-Reply-To: <20080722072109.GA7169@pengutronix.de>
Sascha,
Sascha Hauer said the following on 07/22/2008 02:21 AM:
> Hi,
>
> On Mon, Jul 21, 2008 at 07:15:31PM -0500, Khandenahally, Raghavendra wrote:
>
>
> I would prefer another patch. I didn't watch out when board/omap was
> introduced. In fact, omap is not a board and it's gonna be a mess when
>
I beg to differ on this, we have so many development platforms on
various versions of OMAP all sharing so much board characteristics that
it makes more sense to put all omap boards together in the same
directory. This is to recover from the mess we have had on other
versions where duplication of code was forced due to splitting files
accross. Nothing OMAP specific is put there. it is pure board only
information over here.
Regards,
Nishanth Menon
next prev parent reply other threads:[~2008-07-22 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 0:15 [U-Boot-Users] [Patch 1/3] U-Boot-V2:Board:OMAP common board.h Khandenahally, Raghavendra
2008-07-22 7:21 ` Sascha Hauer
2008-07-22 11:32 ` Nishanth Menon [this message]
2008-07-24 22:30 ` Sascha Hauer
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=4885C541.9090604@gmail.com \
--to=menon.nishanth@gmail.com \
--cc=u-boot@lists.denx.de \
/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