From: Chris Zankel <chris@zankel.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: bad xtensa tree update
Date: Wed, 15 Oct 2008 13:08:40 -0700 [thread overview]
Message-ID: <48F64DC8.70603@zankel.net> (raw)
In-Reply-To: <20081015100906.877efcf0.sfr@canb.auug.org.au>
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.
prev parent reply other threads:[~2008-10-15 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 23:09 linux-next: bad xtensa tree update Stephen Rothwell
2008-10-15 20:08 ` Chris Zankel [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=48F64DC8.70603@zankel.net \
--to=chris@zankel.net \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).