All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Adrian Bunk <bunk@kernel.org>
Subject: Re: 4xx support in arch/ppc is going away Real Soon Now
Date: Sun, 08 Jun 2008 10:54:41 -0500	[thread overview]
Message-ID: <E1K5NE9-000275-2M@jdl.com> (raw)
In-Reply-To: <18506.31325.899081.47718@cargo.ozlabs.ibm.com>

> Grant Likely writes:
> 
> > Oh, and we're going try to create the longest acked-by chain in
> > Linux history.
> 
> Cool :)
> 
> Paul.

So far, I think it looks like this, sorted:

Acked-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Becky Bruce <becky.bruce@freescale.com>
Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
Acked-by: Jochen Friedrich <jochen@scram.de>
Acked-by: Jon Loeliger <jdl@freescale.com>
Acked-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Acked-by: Kumar Gala <galak@kernel.crashing.org>
Acked-by: Olof Johansson <olof@lixom.net>
Acked-by: Peter Korsgaard <jacmet@sunsite.dk>
Acked-by: Scott Wood <scottwood@freescale.com>
Acked-by: Sean MacLennan <smaclennan@pikatech.com>
Acked-by: Segher Boessenkool <segher@kernel.crashing.org>
Acked-by: Stefan Roese <sr@denx.de>
Acked-by: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Acked-by: Wolfgang Denk <wd@denx.de>

I'm not sure, but I _think_ there are a few other PowerPC
developers out there still... :-)

jdl

  reply	other threads:[~2008-06-08 15:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05 14:52 4xx support in arch/ppc is going away Real Soon Now Josh Boyer
2008-06-05 15:11 ` Grant Likely
2008-06-05 15:18   ` Josh Boyer
2008-06-05 15:48     ` Stephen Neuendorffer
2008-06-05 20:12       ` Arnd Bergmann
2008-06-05 20:27         ` Grant Likely
2008-06-05 20:28         ` Olof Johansson
2008-06-05 20:30           ` Scott Wood
2008-06-05 20:37             ` Becky Bruce
2008-06-06 11:19               ` Wolfgang Denk
2008-06-06 15:34                 ` Jon Loeliger
2008-06-06 21:11                   ` Sean MacLennan
2008-06-07  7:36                     ` Peter Korsgaard
2008-06-07 10:07                       ` Stefan Roese
2008-06-08 14:57                         ` Jochen Friedrich
2008-06-08 16:15                           ` Adrian Bunk
2008-06-05 20:40           ` Segher Boessenkool
2008-06-06  4:32         ` Benjamin Herrenschmidt
2008-06-06  4:38           ` Kumar Gala
2008-06-06  8:39             ` Stefan Roese
2008-06-05 18:59     ` 4xx support in " Kumar Gala
2008-06-05 19:13       ` Josh Boyer
2008-06-06 11:53   ` Adrian Bunk
2008-06-06 12:09     ` Paul Mackerras
2008-06-06 17:58       ` Adrian Bunk
2008-06-06 13:56     ` Josh Boyer
2008-06-06 14:53       ` Grant Likely
2008-06-07 12:09         ` Paul Mackerras
2008-06-08 15:54           ` Jon Loeliger [this message]
2008-06-09  7:46             ` Geert Uytterhoeven
2008-06-09 16:21               ` John Linn
2008-06-11 21:31             ` Vitaly Bordug
2008-06-16 14:10             ` Matthias Fuchs
2008-06-16 18:05               ` Josh Boyer

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=E1K5NE9-000275-2M@jdl.com \
    --to=jdl@jdl.com \
    --cc=bunk@kernel.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 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.