linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: linuxppc-dev@ozlabs.org
Subject: Patches added to master & powerpc-next branches of powerpc.git
Date: Tue, 26 Feb 2008 23:03:05 +1100	[thread overview]
Message-ID: <18371.65529.312001.673609@cargo.ozlabs.ibm.com> (raw)

I have created a powerpc-next branch in the powerpc.git tree, which
has the following commits on it so far.  The master branch is at the
same point.  I've pulled in Dave Miller's tree (for the LMB changes)
and applied some other patches from the list.

I'm expecting that platform/subarchitecture maintainers will be
sending me pull requests for their trees from time to time.

Paul.

Anton Vorontsov (1):
      [POWERPC] 8xx: Timebase frequency should not depend on bus-frequency

Badari Pulavarty (1):
      [POWERPC] Add code for removing HPTEs for parts of the linear mapping

Becky Bruce (1):
      [LMB]: Make lmb support large physical addressing

Benjamin Herrenschmidt (1):
      [POWERPC] Fix thinko in cpu_thread_mask_to_cores()

Dale Farnsworth (1):
      [POWERPC] Remove dead code at KernelAltiVec

David S. Miller (2):
      [LIB]: Make PowerPC LMB code generic so sparc64 can use it too.
      [LMB]: Fix bug in __lmb_alloc_base().

Johannes Berg (1):
      [POWERPC] mpic: Make sparse happy

Julia Lawall (1):
      [POWERPC] Use FIELD_SIZEOF in arch/ppc

Kumar Gala (2):
      [LMB]: Fix initial lmb add region with a non-zero base
      [LMB]: Fix lmb_add_region if region should be added at the head

             reply	other threads:[~2008-02-26 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26 12:03 Paul Mackerras [this message]
2008-02-26 14:34 ` Patches added to master & powerpc-next branches of powerpc.git Kumar Gala
2008-02-27  1:24   ` Paul Mackerras
2008-02-27  0:06 ` Benjamin Herrenschmidt
2008-02-27  0:43   ` Paul Mackerras
2008-02-27  0:46     ` 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=18371.65529.312001.673609@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).