From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: linux-omap git tree updated to v2.6.32-rc1, important changes, please read
Date: Wed, 30 Sep 2009 07:07:13 -0700 [thread overview]
Message-ID: <873a64r0fi.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20090928190404.GE18957@atomide.com> (Tony Lindgren's message of "Mon\, 28 Sep 2009 12\:04\:05 -0700")
Tony Lindgren <tony@atomide.com> writes:
> Hi all,
>
> I've updated our linux-omap tree to v2.6.32-rc1. I've also
> added a branch omap-2.6.31 for the old code.
>
> This time I also nuked the remaining omap legacy code we
> still had lurking around :) The commits at the end of this
> mail describe what I did first as commits, then I merged
> everything to be the same as the mainline v2.6.32-rc1.
>
> So currently the linux-omap master branch is:
>
> v2.6.32-rc1 + omap-fixes + ehci + cbus
>
> The new model is that I'll be resetting the linux-omap master
> branch to mainline at each -rc, then merge in our various
> upstream queues back in again.
>
> Please note that "Remove omap extra version in Makefile"
> commit means that you now need to set the ARCH and CROSS_COMPILE
> for your compiler.
FYI... As of 2.6.32, the kernel caches the ARCH and CROSS_COMPILE in
the build dir under include/generated/kernel.[arch,cross_compile], so
if you build using ARCH and CROSS_COMPILE once, it should remember
them until doing a clean build.
Kevin
next prev parent reply other threads:[~2009-09-30 14:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 19:04 linux-omap git tree updated to v2.6.32-rc1, important changes, please read Tony Lindgren
2009-09-28 21:54 ` Kalle Valo
2009-09-29 14:36 ` green
2009-09-29 10:54 ` Shilimkar, Santosh
2009-09-30 17:55 ` Tony Lindgren
2009-10-01 4:04 ` Shilimkar, Santosh
2009-09-29 17:24 ` Felipe Contreras
2009-09-29 18:26 ` Tony Lindgren
2009-09-29 19:20 ` Alexander Shishkin
2009-09-29 19:26 ` Aguirre Rodriguez, Sergio Alberto
2009-09-29 19:42 ` Alexander Shishkin
2009-09-29 19:30 ` Tony Lindgren
2009-09-29 19:41 ` Alexander Shishkin
2009-09-30 15:53 ` Roger Quadros
2009-09-30 17:02 ` Alexander Shishkin
2009-09-30 17:04 ` Gadiyar, Anand
2009-09-30 17:31 ` Tony Lindgren
2009-10-01 7:30 ` Roger Quadros
2009-10-01 7:58 ` Alexander Shishkin
2009-10-01 8:06 ` Roger Quadros
2009-10-01 8:30 ` Roger Quadros
2009-10-01 8:31 ` Roger Quadros
2009-10-01 7:58 ` Roger Quadros
2009-09-30 14:07 ` Kevin Hilman [this message]
2009-09-30 17:25 ` Tony Lindgren
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=873a64r0fi.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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