* linux-next: bad xtensa tree update
@ 2008-10-14 23:09 Stephen Rothwell
2008-10-15 20:08 ` Chris Zankel
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2008-10-14 23:09 UTC (permalink / raw)
To: Chris Zankel; +Cc: linux-next
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
Hi Chris,
I fetched the xtensa tree this morning and it now points to
next-20080919. The trees merged into linux-next should never depend on
linux-next itself. I have reverted the xtensa tree to what is was
yesterday (commit dbd3dca "xtensa: use newer __SPIN_LOCK_UNLOCKED
macro"). Pleas fix up your tree.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linux-next: bad xtensa tree update
2008-10-14 23:09 linux-next: bad xtensa tree update Stephen Rothwell
@ 2008-10-15 20:08 ` Chris Zankel
0 siblings, 0 replies; 2+ messages in thread
From: Chris Zankel @ 2008-10-15 20:08 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next
Hi Stephen,
Tree should be fixed again.
Do you have an update or better explanation to the instructions on
http://lwn.net/Articles/289245/? When I follow those instructions, I end
up with a linux-next tree, or are the 'rebase --onto' instructions meant
to be used for a separate branch only?
Thanks,
-Chris
Stephen Rothwell wrote:
> I fetched the xtensa tree this morning and it now points to
> next-20080919. The trees merged into linux-next should never depend on
> linux-next itself. I have reverted the xtensa tree to what is was
> yesterday (commit dbd3dca "xtensa: use newer __SPIN_LOCK_UNLOCKED
> macro"). Pleas fix up your tree.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-10-15 20:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-14 23:09 linux-next: bad xtensa tree update Stephen Rothwell
2008-10-15 20:08 ` Chris Zankel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).