From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-serial@vger.kernel.org, Benjamin Krill <ben@codiert.org>,
linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
Josh Boyer <jwboyer@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] serial: add support for the cell network processor NWP device
Date: Wed, 07 Jan 2009 14:08:14 +1100 [thread overview]
Message-ID: <1231297694.14860.55.camel@pasglop> (raw)
In-Reply-To: <200811241453.32166.arnd@arndb.de>
On Mon, 2008-11-24 at 14:53 +0100, Arnd Bergmann wrote:
> From: Benjamin Krill <ben@codiert.org>
>
> Add support for the nwp serial device which is connected to a DCR bus. It
> uses the of_serial device driver to determine necessary properties from
> the device tree. The supported device is added as serial port number 84.
>
> NWP stands for network processor and it is part of the QPACE - Quantum
> Chromodynamics Parallel Computing on the Cell Broadband Engine project.
> The implementation is a lightweight uart implementation with the focus
> to consume as little resources as possible and it is connected to a
> DCR bus.
>
> Signed-off-by: Benjamin Krill <ben@codiert.org>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
There have been no comment nor objection about this patch.
Andrew, do we have a serial maintainer or should I merge it via the
powerpc tree ?
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] serial: add support for the cell network processor NWP device
Date: Wed, 07 Jan 2009 14:08:14 +1100 [thread overview]
Message-ID: <1231297694.14860.55.camel@pasglop> (raw)
In-Reply-To: <200811241453.32166.arnd@arndb.de>
On Mon, 2008-11-24 at 14:53 +0100, Arnd Bergmann wrote:
> From: Benjamin Krill <ben@codiert.org>
>
> Add support for the nwp serial device which is connected to a DCR bus. It
> uses the of_serial device driver to determine necessary properties from
> the device tree. The supported device is added as serial port number 84.
>
> NWP stands for network processor and it is part of the QPACE - Quantum
> Chromodynamics Parallel Computing on the Cell Broadband Engine project.
> The implementation is a lightweight uart implementation with the focus
> to consume as little resources as possible and it is connected to a
> DCR bus.
>
> Signed-off-by: Benjamin Krill <ben@codiert.org>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
There have been no comment nor objection about this patch.
Andrew, do we have a serial maintainer or should I merge it via the
powerpc tree ?
Cheers,
Ben.
next prev parent reply other threads:[~2009-01-07 3:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 13:53 [PATCH v2] serial: add support for the cell network processor NWP device Arnd Bergmann
2008-11-24 13:53 ` Arnd Bergmann
2009-01-07 3:08 ` Benjamin Herrenschmidt [this message]
2009-01-07 3:08 ` Benjamin Herrenschmidt
2009-01-07 4:21 ` Andrew Morton
2009-01-07 4:21 ` Andrew Morton
2009-01-07 8:11 ` Benjamin Krill
2009-01-07 8:11 ` Benjamin Krill
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=1231297694.14860.55.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ben@codiert.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-serial@vger.kernel.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 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.