linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: 2.6.27-rc1 problems
Date: Wed, 30 Jul 2008 07:33:05 +1000	[thread overview]
Message-ID: <1217367185.11188.260.camel@pasglop> (raw)
In-Reply-To: <20080729140617.7bf16aeb@lappy.seanm.ca>

On Tue, 2008-07-29 at 14:06 -0400, Sean MacLennan wrote:
> I am seeing a lot of problems with 2.6.27-rc1.
> 
> Merge conflicts that make no sense.

Ugh ? Have you done a clean pull ?

> Files missing (tracehook.h).

Looks like your repo isn't sane

> Lots of compile errors.

There's one known due to a PCI patch that went in and broke ppc64 but
that's it I think. I'll a new batch of fixes today.

> Anybody else seeing problems, or is it just me? I am starting
> to wonder if my git repository has gotten corrupted.

Yeah, sounds like it.

Ben.

  reply	other threads:[~2008-07-29 21:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 18:06 2.6.27-rc1 problems Sean MacLennan
2008-07-29 21:33 ` Benjamin Herrenschmidt [this message]
2008-07-29 21:50   ` Sean MacLennan
2008-07-29 22:01     ` Benjamin Herrenschmidt

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=1217367185.11188.260.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=smaclennan@pikatech.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;
as well as URLs for NNTP newsgroup(s).