From: Benjamin Krill <ben@codiert.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-serial@vger.kernel.org, linuxppc-dev@ozlabs.org,
Josh Boyer <jwboyer@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] serial: add support for the cell network processor NWP device
Date: Wed, 7 Jan 2009 09:11:21 +0100 [thread overview]
Message-ID: <20090107081120.GB3306@codiert.org> (raw)
In-Reply-To: <20090106202143.b31b908e.akpm@linux-foundation.org>
>My version is mucked up anyway - PORT_NWPSERIAL has the same value as
>PORT_S3C6400.
Should I send an updated version against a current tree?
ben
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Krill <ben@codiert.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-serial@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2] serial: add support for the cell network processor NWP device
Date: Wed, 7 Jan 2009 09:11:21 +0100 [thread overview]
Message-ID: <20090107081120.GB3306@codiert.org> (raw)
In-Reply-To: <20090106202143.b31b908e.akpm@linux-foundation.org>
>My version is mucked up anyway - PORT_NWPSERIAL has the same value as
>PORT_S3C6400.
Should I send an updated version against a current tree?
ben
next prev parent reply other threads:[~2009-01-07 8:43 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
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 [this message]
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=20090107081120.GB3306@codiert.org \
--to=ben@codiert.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.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.