From: Kevin Hilman <khilman@mvista.com>
To: "Syed Mohammed, Khasim" <x0khasim@ti.com>
Cc: Linux OMAP <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH 1/12] Add VFP support for ARM V7 - OMAP 3430 support
Date: Thu, 31 May 2007 14:33:54 -0700 [thread overview]
Message-ID: <465F3F42.1020805@mvista.com> (raw)
In-Reply-To: <9C23CDD79DA20A479D4615857B2E2C470106320C@dlee13.ent.ti.com>
Syed Mohammed, Khasim wrote:
> Add VFP support for ARM V7, derived from ARM's Cortex patch
>
Sorry to not speak up sooner, but I think we need to rebase this whole patchset on top of Catalin's ARMv7 patches which he has in his tree[1]
I just did a quick test and all his patches apply cleanly to the current OMAP git tree. Here's the git magic for how I do it: (you might need a recent git for this, I use 1.5.2)
$ git remote add arm git://linux-arm.org/linux-2.6.git
Then fetch his changes into your repo
$ git fetch arm
Then cherry-pick the commits from his tree into your tree. To me it seems like the following range is useful his ARMv7 + NEON + VFP3 + Thumb-2 userland support:
$ git-rev-list --reverse arm/origin..654441661e3655df22fb7b85a7fc64201c09f4d0
Then, cherry-pick them into your OMAP tree (this cmd should be all on one line)
$ for commit in `git-rev-list --reverse arm/origin..654441661e3655df22fb7b85a7fc64201c09f4d0`; do git-cherry-pick -x ${commit}; done
Kevin
[1] http://www.linux-arm.org/git
next prev parent reply other threads:[~2007-05-31 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 17:57 [PATCH 1/12] Add VFP support for ARM V7 - OMAP 3430 support Syed Mohammed, Khasim
2007-05-31 21:33 ` Kevin Hilman [this message]
2007-05-31 21:58 ` Syed Mohammed, Khasim
2007-06-01 22:37 ` Syed Mohammed, Khasim
-- strict thread matches above, loose matches on Subject: below --
2007-06-01 22:38 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=465F3F42.1020805@mvista.com \
--to=khilman@mvista.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=x0khasim@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 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.