From: David Woodhouse <dwmw2@infradead.org>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Marcin Gibu?a <mg@iceni.pl>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: phram problems and patch
Date: Mon, 13 Dec 2004 17:31:58 +0000 [thread overview]
Message-ID: <1102959118.13016.5.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <20041213172816.GB27124@wohnheim.fh-wedel.de>
On Mon, 2004-12-13 at 18:28 +0100, Jörn Engel wrote:
> According to David, it's on it's way.
It's on its way and is already in the -mm tree. Should be in Linus' tree
soon after 2.6.10 is released.
> There are more patches pending, though.
Assuming you mean the other bits you already committed to CVS, those are
in bk://linux-mtd.bkbits.net/mtd-2.6 as of this morning, and should
hence be in the next -mm release too.
--
dwmw2
next prev parent reply other threads:[~2004-12-13 17:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 17:05 phram problems and patch Marcin Gibuła
2004-12-13 17:28 ` Jörn Engel
2004-12-13 17:31 ` David Woodhouse [this message]
2004-12-13 17:35 ` Jörn Engel
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=1102959118.13016.5.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mg@iceni.pl \
/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