From: Paul Mackerras <paulus@samba.org>
To: linuxppc-dev@ozlabs.org
Subject: Re: Commits added to powerpc.git master and powerpc-next branches
Date: Tue, 1 Jul 2008 12:01:27 +1000 [thread overview]
Message-ID: <18537.36855.55783.264374@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <18537.34789.355993.604857@cargo.ozlabs.ibm.com>
I wrote:
> Hold off from pulling this for now, everyone... I inadvertently broke
> builds with 64k pages by leaving in some stuff that was purely for
> testing in my "Only demote individual slices rather than whole
> process" patch. I'll re-do the tree in order to avoid breaking
> bisection.
I have redone the tree now. If you have pulled within the last one
and a half hours, you'll need to do a git pull -f. Sorry about that.
Paul.
next prev parent reply other threads:[~2008-07-01 2:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 0:20 Commits added to powerpc.git master and powerpc-next branches Paul Mackerras
2008-07-01 1:27 ` Paul Mackerras
2008-07-01 1:45 ` Benjamin Herrenschmidt
2008-07-01 2:30 ` Josh Boyer
2008-07-01 2:44 ` Benjamin Herrenschmidt
2008-07-01 4:05 ` Kumar Gala
2008-07-01 2:01 ` Paul Mackerras [this message]
2008-07-01 4:01 ` [PATCH 0/2] powerpc: Update VSX support Michael Neuling
2008-07-01 4:01 ` [PATCH 2/2] powerpc: Update for VSX core file and ptrace Michael Neuling
2008-07-01 4:01 ` [PATCH 1/2] powerpc: Fix compile error for CONFIG_VSX Michael Neuling
2008-07-01 4:51 ` Michael Neuling
2008-07-01 7:00 ` [PATCH] powerpc: fix compile warning in init_thread Michael Neuling
2008-07-01 9:07 ` Benjamin Herrenschmidt
2008-07-01 11:02 ` Michael Neuling
2008-07-01 8:49 ` Commits added to powerpc.git master and powerpc-next branches Laurent Pinchart
2008-07-01 15:54 ` Jochen Friedrich
2008-07-02 7:42 ` Kumar Gala
2008-07-02 12:35 ` Jochen Friedrich
2008-07-02 15:10 ` Kumar Gala
2008-07-02 7:41 ` Kumar Gala
2008-07-02 8:41 ` Laurent Pinchart
2008-07-02 1:56 ` [PATCH] powerpc: cleanup copy_to/from_user for vsx and fpr Michael Neuling
2008-07-02 4:06 ` Michael Neuling
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=18537.36855.55783.264374@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@ozlabs.org \
/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).