linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Yet more patches added to for-2.6.25/master branches
Date: Sun, 23 Dec 2007 18:23:18 +1100	[thread overview]
Message-ID: <18682.1198394598@neuling.org> (raw)
In-Reply-To: <18283.44454.618519.155696@cargo.ozlabs.ibm.com>

Paulus,

Can you take the crash shutdown hook patches as well for 2.6.25?

http://patchwork.ozlabs.org/linuxppc/patch?person=414&id=15546
http://patchwork.ozlabs.org/linuxppc/patch?person=414&id=15547

Mikey


In message <18283.44454.618519.155696@cargo.ozlabs.ibm.com> you wrote:
> Aegis Lin (1):
>       [POWERPC] spufs: Use separate timer for /proc/spu_loadavg calculation
> 
> Andre Detsch (1):
>       [POWERPC] spufs: DMA Restart after SIGSEGV
> 
> Arnd Bergmann (1):
>       [POWERPC] spufs: block fault handlers in spu_acquire_runnable
> 
> Benjamin Herrenschmidt (2):
>       [POWERPC] Fix for via-pmu based backlight control
>       [POWERPC] Fix possible NULL deref in ppc32 PCI
> 
> Christoph Hellwig (2):
>       [POWERPC] spufs: add enchanced simple attr macros
>       [POWERPC] spufs: make state_mutex interruptible
> 
> Emil Medve (1):
>       [POWERPC] Optimize counting distinct entries in the relocation sections
> 
> Jeremy Kerr (5):
>       [POWERPC] spufs: move fault, lscsa_alloc and switch code to spufs modul
e
>       [POWERPC] spufs: fix incorrect interrupt status clearing in backing mbo
x stat poll
>       [POWERPC] spufs: use #defines for SPU class [012] exception status
>       [POWERPC] spufs: rework class 0 and 1 interrupt handling
>       [POWERPC] spufs: Don't leak kernel stack through an empty {i,m}box_info
 read
> 
> Julio M. Merino Vidal (1):
>       [POWERPC] spufs: fix typos in sched.c comments
> 
> Luke Browning (4):
>       [POWERPC] spufs: add backing ops for privcntl register
>       [POWERPC] spufs: reorganize spu_run_init
>       [POWERPC] spufs: spu_find_victim may choose wrong victim
>       [POWERPC] spufs: decouple spu scheduler from spufs_spu_run (asynchronou
s scheduling)
> 
> Masato Noguchi (2):
>       [POWERPC] cell: wrap master run control bit
>       [POWERPC] spufs: don't set reserved bits in spu interrupt status
> 
> Scott Wood (1):
>       [POWERPC] Implement arch disable/enable irq hooks.
> 
> Stephen Rothwell (5):
>       [POWERPC] Add EHEA and EHCA as modules in the ppc64_defconfig
>       [POWERPC] The builtin matches for ibmebus.c can be __initdata
>       [POWERPC] Constify the of_device_id passed to of_platform_bus_probe
>       [POWERPC] Pointers marked as __iomem do not need to be volatile
>       [POWERPC] Make non-PCI build work again
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
> 

      parent reply	other threads:[~2007-12-23  7:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 12:12 Yet more patches added to for-2.6.25/master branches Paul Mackerras
2007-12-21 12:37 ` Arnd Bergmann
2007-12-21 14:13 ` Marian Balakowicz
2007-12-21 15:29   ` Kumar Gala
2007-12-21 17:34   ` Grant Likely
2007-12-21 18:07     ` Marian Balakowicz
2007-12-21 18:13       ` Grant Likely
2007-12-21 18:25         ` Marian Balakowicz
2007-12-22 10:56 ` David Woodhouse
2007-12-23 23:32   ` Paul Mackerras
2007-12-23  7:23 ` Michael Neuling [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=18682.1198394598@neuling.org \
    --to=mikey@neuling.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).