public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: tom_gall@vnet.ibm.com
Cc: Tom Rini <trini@kernel.crashing.org>,
	reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-list] Re: Linux 2.4.12-ac1
Date: Sat, 13 Oct 2001 00:30:33 +0400	[thread overview]
Message-ID: <3BC752E9.171FB08E@namesys.com> (raw)
In-Reply-To: <20011012072910.N21564@cpe-24-221-152-185.az.sprintbbd.net> <E15s44B-0007Vk-00@the-village.bc.nu> <20011012083616.C9992@cpe-24-221-152-185.az.sprintbbd.net> <3BC71084.ECCD2E4B@vnet.ibm.com>

Tom Gall wrote:
> 
> Tom Rini wrote:
> >
> > On Fri, Oct 12, 2001 at 04:17:39PM +0100, Alan Cox wrote:
> > > > On Fri, Oct 12, 2001 at 02:17:26PM +0100, Alan Cox wrote:
> > > >
> > > > > 2.4.12-ac1
> > > > > o Merge the majority of 2.4.11/12
> > > > >   -       Fall back to the Linus reiserfs code set
> > > > [snip]
> > > >
> > > > The endian-safe patches will come back tho, right?  I don't think those
> > > > have made it into Linus' tree yet...
> > >
> > > Really what needs to happen is the important bits that were tested and
> > > the reiser folks were happy with get pushed back bit by bit into both trees
> > > now
> > [reiserfs list added to cc]
> >
> > That would be nice.  Are there any plans on behalf of the reiserfs
> > people to merge in the Endian-Safeness patches now?
> 
> Speaking from the PPC64 crew, this would be highly desirable.
> 
> Regards,
> 
> Tom
> 
> --
> Tom Gall - PPC64 Code Monkey     "Where's the ka-boom? There was
> Linux Technology Center           supposed to be an earth
> (w) tom_gall@vnet.ibm.com         shattering ka-boom!"
> (w) 507-253-4558                 -- Marvin Martian
> (h) tgall@rochcivictheatre.org
> http://www.ibm.com/linux/ltc/projects/ppc

Patch has been sent to Linus.  It will be resent to him and ac now that a new
release has come out.

Hans

  reply	other threads:[~2001-10-12 20:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 13:17 Linux 2.4.12-ac1 Alan Cox
2001-10-12 14:04 ` Udo A. Steinberg
2001-10-12 18:06   ` Rui Sousa
2001-10-12 18:13     ` Udo A. Steinberg
2001-10-12 19:22       ` Rui Sousa
2001-10-12 19:40         ` Udo A. Steinberg
2001-10-12 14:29 ` Tom Rini
2001-10-12 15:17   ` Alan Cox
2001-10-12 15:36     ` Tom Rini
2001-10-12 15:47       ` Tom Gall
2001-10-12 20:30         ` Hans Reiser [this message]
2001-10-12 15:55       ` (memory?) bug between 2.4.9-ac10 and -ac14 Mikael Johansson
2001-10-12 17:18       ` [reiserfs-list] Re: Linux 2.4.12-ac1 Chris Mason
2001-10-12 21:26 ` J . A . Magallon
2001-10-12 21:52   ` Rik van Riel
2001-10-12 22:04     ` J . A . Magallon
2001-10-12 23:24 ` Thomas Davis
2001-10-13  4:06 ` Tom Vier
2001-10-14  1:34 ` Tom Rini
2001-10-14  1:34 ` Tom Rini

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=3BC752E9.171FB08E@namesys.com \
    --to=reiser@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@namesys.com \
    --cc=tom_gall@vnet.ibm.com \
    --cc=trini@kernel.crashing.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