From: tony@atomide.com
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: ARCH_OMAP243x vs. ARCH_OMAP2430
Date: Tue, 3 Apr 2007 15:54:26 -0400 [thread overview]
Message-ID: <20070403195424.GF24864@atomide.com> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D9130274298A29FE@dlee13.ent.ti.com>
* Woodruff, Richard <r-woodruff2@ti.com> [070313 20:02]:
> > But in the MUSB code as well as prcm-regs.h there are #ifdefs for
> > OMAP243X. Are there other 243x platforms in the wild, or should I
> just
> > convert these #ifdefs to 2430. If converting is the right thing,
> here's
> > a patch.
>
> Those 243X's are used in MV and TI trees. I don't think the GIT one
> used it. They probably snuck in on your end or in previous pushes
> candidates from others.
>
> They all have to be the same for sure. Looks like a good thing to fix.
This is now pushed too.
Tony
prev parent reply other threads:[~2007-04-03 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 23:51 ARCH_OMAP243x vs. ARCH_OMAP2430 Kevin Hilman
2007-03-14 0:01 ` Woodruff, Richard
2007-04-03 19:54 ` tony [this message]
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=20070403195424.GF24864@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@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