All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc44x: support for 256K PAGE_SIZE
Date: Tue, 23 Oct 2007 16:00:34 +0200	[thread overview]
Message-ID: <3192bd670c4e7814de0deb85a8556528@kernel.crashing.org> (raw)
In-Reply-To: <20071018070139.339e2efb@weaponx.rchland.ibm.com>

> Requiring a modified binutils makes me a bit nervous though.

As long as those binutils modifications are sent upstream, I don't
see the problem?  If not, this would be a blocker IMHO.


Segher

  parent reply	other threads:[~2007-10-23 14:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18  7:08 [PATCH] ppc44x: support for 256K PAGE_SIZE Yuri Tikhonov
2007-10-18 10:44 ` Josh Boyer
2007-10-18 11:45   ` Benjamin Herrenschmidt
2007-10-18 12:01     ` Josh Boyer
2007-10-18 12:12       ` Benjamin Herrenschmidt
2007-10-18 13:25         ` Yuri Tikhonov
2007-10-23 14:00       ` Segher Boessenkool [this message]
2007-10-18 13:18   ` Yuri Tikhonov
2007-10-18 13:25     ` Josh Boyer
2007-10-18 13:30       ` Yuri Tikhonov
2007-10-18 14:41         ` Josh Boyer
2007-10-18 23:21 ` Paul Mackerras
2007-10-19 13:24   ` Kumar Gala
2007-10-22 16:12     ` Yuri Tikhonov
2007-10-23 13:59       ` Segher Boessenkool
2007-10-23 23:08         ` Paul Mackerras
2007-10-23 23:15       ` Paul Mackerras
2007-10-19 15:37   ` Yuri Tikhonov
2007-10-19 15:48     ` Kumar Gala
2007-10-19 16:03       ` Yuri Tikhonov
2007-10-19 16:36 ` Josh Boyer
2007-10-19 19:04   ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2007-10-18 11:00 Yuri Tikhonov
2007-10-18 11:47 ` Benjamin Herrenschmidt
2007-10-18 13:20   ` Yuri Tikhonov

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=3192bd670c4e7814de0deb85a8556528@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.