linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, mingo@elte.hu
Subject: Re: [PATCH] powerpc: Fix DEBUG_HIGHMEM build break from d4515646699
Date: Tue, 01 Dec 2009 07:16:29 +1100	[thread overview]
Message-ID: <1259612189.2076.102.camel@pasglop> (raw)
In-Reply-To: <20091130195435.GE2937@zod.rchland.ibm.com>


> When you say you'll see what you can do, do you mean you'll see if you can get
> the patch into .32, or change the Fedora config?  If you mean change the Fedora
> config, I can do that myself.  I was more pointing out that you have a .32
> patch not needed for .33 heading for .33... ;)

I'll try to get the patch in later today

Cheers,
Ben.

      reply	other threads:[~2009-11-30 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 22:28 [PATCH] powerpc: Fix DEBUG_HIGHMEM build break from d4515646699 Becky Bruce
2009-11-30 17:57 ` Josh Boyer
2009-11-30 19:49   ` Benjamin Herrenschmidt
2009-11-30 19:54     ` Josh Boyer
2009-11-30 20:16       ` Benjamin Herrenschmidt [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=1259612189.2076.102.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@elte.hu \
    /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).