From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Chris Zankel <chris@zankel•net>
Cc: linux-next@vger•kernel.org
Subject: linux-next: bad xtensa tree update
Date: Wed, 15 Oct 2008 10:09:06 +1100 [thread overview]
Message-ID: <20081015100906.877efcf0.sfr@canb.auug.org.au> (raw)
[-- 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 --]
next reply other threads:[~2008-10-14 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 23:09 Stephen Rothwell [this message]
2008-10-15 20:08 ` linux-next: bad xtensa tree update Chris Zankel
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=20081015100906.877efcf0.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=chris@zankel$(echo .)net \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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