From: Sven Luther <sven.luther@wanadoo.fr>
To: Christoph Hellwig <hch@lst.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: status of pegasos2 support
Date: Sun, 9 Jan 2005 13:31:11 +0100 [thread overview]
Message-ID: <20050109123111.GB17561@pegasos> (raw)
In-Reply-To: <20050109115935.GA19249@lst.de>
On Sun, Jan 09, 2005 at 12:59:36PM +0100, Christoph Hellwig wrote:
> Guys, could we please get some definit comments on the Pegasos2 support?
>
> We've been carring it around forever in the Debian tree and it's been
> making no progress at all.
As for me, it is ready to be submitted upstream, i sent it already, and it was
mostly ok when i wrote to linuxppc-dev and i think benh also said they are ok.
I believe benh is waiting to go back home (should be in the plane right now if
i am not wrong) to do the submission part of it.
Friendly,
Sven Luther
prev parent reply other threads:[~2005-01-09 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 11:59 status of pegasos2 support Christoph Hellwig
2005-01-09 12:31 ` Sven Luther [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=20050109123111.GB17561@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=hch@lst.de \
--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).